-
August 19th, 2010, 02:17 PM
#1
When you say "LS was not get started", do you mean that issues may occur during startup or that you may deliberately not restart the Server (or something else, of course)?
It was the another situation, Whenever LS not run on the server, If the users try to login means, intimate the users with alert message. How to resolve this?
-
August 20th, 2010, 08:44 AM
#2
I confirm that the web client library makes no assumption about the unavailability of the Server and just keeps retrying to connect.
At application level, you can leverage onStatusChange or getStatus and check how long the Engine remains in "CONNECTING" state with your own timer;
if needed, you can switch to "DISCONNECTED" state, then issue an alert.
Similar Threads
-
By magnum_rg in forum Client SDKs
Replies: 5
Last Post: August 12th, 2011, 09:43 AM
-
By phancongphuoc in forum Client SDKs
Replies: 1
Last Post: December 20th, 2010, 08:49 AM
-
By vaduganathan in forum Adapter SDKs
Replies: 1
Last Post: May 28th, 2010, 09:34 AM
-
By vaduganathan in forum Client SDKs
Replies: 1
Last Post: May 12th, 2010, 09:26 AM
-
By churrusco in forum General
Replies: 15
Last Post: April 20th, 2010, 08:46 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 11:01 AM.
Bookmarks