-
August 11th, 2009, 10:14 AM
#1
Though Lightstreamer was conceived for the handling of small updates,
updates on the order of the MB are handled successfully on some existing applications using thick clients.
On web browsers, we expect that browser limitations may affect the processing of very huge updates; however
- there are no constraints related to limitations on cookie management
- no further constraint is applied when sharing the engine
The same holds for sendMessage.
Note that the <content_length> settings in the Server configuration file should be far greater than the expected update length (but, in case of conflicts, the update takes the precedence).
Similarly, note that the <request_limit> protection setting in the Server configuration file should be far greater than the expected client message length; in this case the Server setting takes the precedence.
Note that updates and messages are sent in encoded form and this may increase their length, depending on the contents.
-
August 11th, 2009, 03:34 PM
#2
Thanks -- that's very helpful!
Similar Threads
-
By felipe.valemobi in forum Client SDKs
Replies: 1
Last Post: October 19th, 2011, 11:33 AM
-
By sfs123 in forum Client SDKs
Replies: 1
Last Post: July 13th, 2011, 09:13 AM
-
By GoatHunter in forum General
Replies: 2
Last Post: August 25th, 2009, 10:54 AM
-
By deltron0 in forum Client SDKs
Replies: 2
Last Post: May 15th, 2008, 09:25 AM
-
By indrajit in forum Client SDKs
Replies: 1
Last Post: February 22nd, 2008, 08:41 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 10:20 PM.
Bookmarks