-
March 5th, 2015, 09:30 AM
#1
Let me clarify the point with LSConnectionInfo->pollingSecs.
This parameter is usually 0.
This means that, in case of polling, a pure long polling is performed.
In this case, Lightstreamer does its best effort to send to the client all available updates;
as a consequence, any frequency limit settings, like LSExtendedTableInfo->requestedMaxFrequency, will be the only limits that will apply.
On the other hand, if you set it as nonzero, it forces a client-side pause between subsequent polls, which brings you in a synchronous polling scenario.
In this case, if the frequency of polls is lower than the LSExtendedTableInfo->requestedMaxFrequency setting of some item, it takes the precedence and lowers the update frequency seen by the application.
Note that this behavior has not changed.
Similar Threads
-
By Anatoly Gurfinkel in forum Client SDKs
Replies: 9
Last Post: July 6th, 2015, 04:24 PM
-
By LS_Developer in forum Client SDKs
Replies: 3
Last Post: February 14th, 2013, 02:47 PM
-
By mibrahim.youxel in forum Client SDKs
Replies: 4
Last Post: December 3rd, 2012, 09:49 AM
-
By bor306 in forum Client SDKs
Replies: 7
Last Post: July 11th, 2012, 02:28 PM
-
By Alessandro in forum Client SDKs
Replies: 0
Last Post: March 28th, 2011, 03:06 PM
Tags for this Thread
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 03:19 PM.
Bookmarks