-
July 25th, 2014, 09:05 AM
#3
Well,
since you would still have to hit the server to verify if you can connect or not, I would suggest to go with the LightstreamerClient connection, then listen for the DISCONNECTED* events and change the server on the connectionDetails element to try the next one ( http://www.lightstreamer.com/distros...tServerAddress )
Since both the events and the API calls are asynchronously executed, a new connection may be created before the server address setting is changed, so I would add an explicit disconnect call before changing the server and a connect call after it.
Note that the connection efforts might fail immediately or might remain pending. In the latter case a timeout is waited before giving up the connection. You could reduce such timeout ( http://www.lightstreamer.com/distros...ConnectTimeout )
Also, when connecting, the client by the default sends an http request and concurrently opens a websocket. You might want to delay the websocket ( http://www.lightstreamer.com/distros...yWSOpenEnabled )
HTH
Similar Threads
-
Replies: 1
Last Post: November 19th, 2010, 11:41 AM
-
By PeterHiross in forum General
Replies: 2
Last Post: August 25th, 2010, 04:27 PM
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 06:50 AM.
Bookmarks