Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha2, 2.0-Alpha3
-
Fix Version/s: 2.0.0
-
Component/s: Push Library
-
Labels:None
-
Environment:ICEpush
Description
The JavaScript Bridge does not try to establish the blocking connection again, after it has been severed.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Introduced connection inactivity mechanism. The mechanism assumes that the blocking connection is regularly unblocked by the server-side heartbeat. When no response (connection unblocked) is received after a period of time (equal to the heartbeat period) the blocking connection is re-initiated. A second try is initiated if necessary after which the blocking connection is considered to be down (server not responding or no network access).
Show
Mircea Toma
added a comment - Introduced connection inactivity mechanism. The mechanism assumes that the blocking connection is regularly unblocked by the server-side heartbeat. When no response (connection unblocked) is received after a period of time (equal to the heartbeat period) the blocking connection is re-initiated. A second try is initiated if necessary after which the blocking connection is considered to be down (server not responding or no network access).
Here's why severed connections cannot be detected on the client: http://windyroad.org/2006/08/16/ajax-error-handling/
Show
Mircea Toma
added a comment - Here's why severed connections cannot be detected on the client: http://windyroad.org/2006/08/16/ajax-error-handling/
Assigning to Mircea for investigation.