-
May 21st, 2009, 09:37 AM
#1
Hi Richard,
As I mentioned in this post, the reconnection caused by a content-length exhaustion is totally transparent to both the application and the user, and no status change at all happens.
If you observed a status change, this was just a coincidence, probably caused a network problem or by the client CPU saturation. The transition to STALLED state cannot be related to the content-length.
Do you have the detailed server-side logs showing the life-cycle of the user session that experimented the issue?
Similar Threads
-
By LS_Developer in forum General
Replies: 3
Last Post: March 14th, 2012, 02:46 PM
-
By LS_Developer in forum Client SDKs
Replies: 3
Last Post: March 6th, 2012, 08:58 AM
-
By mr_gray in forum Client SDKs
Replies: 5
Last Post: December 20th, 2010, 01:37 PM
-
By patilgkk in forum General
Replies: 5
Last Post: August 2nd, 2010, 09:04 AM
-
By venkihere in forum Client SDKs
Replies: 7
Last Post: October 12th, 2007, 01:14 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 07:19 PM.
Bookmarks