-
August 31st, 2009, 11:16 AM
#2
Yes, you just need to implement onServerError, identify the specific case and force STREAMING again.
This is not the default, because onServerError is usually called when the problem is not recoverable by a new connection attempt. For instance, the connection may have been forcibly interrupted because of a limit on the overall number of sessions.
If you reconnect in any case, consider that this may not always be the best handling of the case.
However, if a firewall simply breaks a connection, this should not cause an "Error 30". Can you find more information on what happens in those situations?
Note that, with the next release of Lightstreamer, the specific cause of the interruption will be available to the client and all available error codes, between 30 and 39, will be used.
Similar Threads
-
By lethanhclub in forum Adapter SDKs
Replies: 6
Last Post: September 16th, 2009, 10:26 AM
-
By kalski in forum Client SDKs
Replies: 3
Last Post: July 31st, 2008, 09:14 AM
-
By kg_can in forum Client SDKs
Replies: 1
Last Post: March 7th, 2008, 09:11 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 02:08 PM.
Bookmarks