-
October 12th, 2009, 10:56 AM
#6
Hi Dario,
Looking at a previous post, I have seen that you mentioned that the following logic is implemented in the Lightstreamer server:
if isSnapshotAvailable(item) == true
[SNAP] [EOS] UPD*
else
UPD*
with the following comment:
"However, redundant SNAP events, after generating the reported log line, are just converted into UPD events; so, they are NOT DISCARDED."
I would like to understand if there is any special reason why Lightstreamer is reporting the exception in the logs for the additional snapshot provided and if this has any effect in the behavior / performance of the Lightstreamer Server, apart the line in the logs.
As in the case of our data adapter, I see it as a possible common behavior in certain publisher/subscriber APIs to provide multiple snapshots to "resume" or "refresh" an item, therefore I would like to understand whether Lightstreamer is thinking of managing this, with either a configuration or an extension of your API.
The alternative for our own data adapter would be to implement a stateful logic as opposed to the current stateless one, converting to simple updates all the snapshots of an item following the first one.
Let me know if you need any further detail to better understand by request.
Thanks a lot in advance,
Pradeep
Similar Threads
-
By finodex in forum Adapter SDKs
Replies: 5
Last Post: May 14th, 2012, 01:47 PM
-
By colmfield in forum Client SDKs
Replies: 2
Last Post: August 26th, 2010, 09:52 AM
-
By RichPratt in forum Adapter SDKs
Replies: 7
Last Post: June 7th, 2010, 09:38 AM
-
By sukhdev in forum Adapter SDKs
Replies: 3
Last Post: August 1st, 2007, 08:44 AM
-
By churrusco in forum General
Replies: 2
Last Post: May 4th, 2007, 03:19 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 05:12 AM.
Bookmarks