Results 1 to 8 of 8

Threaded View

  1. #5
    Senior Member
    Join Date
    Jul 2013
    Posts
    39
    Thanks Marco,

    - The client connects to the LS Server, subscribes to an item, and receives the snapshot and than all the updates.
    - at a certain point the client decides to suspend the subscription because it goes in background or even stops, but in any case it is able to retain the last snapshot of the received data.
    - after a while, that can be minutes or also hour, the client resumes, and it wants to receive only the date not received in the previous session.
    Correct.

    The question is for how long the client is supposed to suspend the subscription, because a session cannot last long.
    We can have a timeout option for this case.

    The key point in this scenario is the fact that the client is actually closing the old session and opening a new one, but wants to receive only the data not received in the previous session.
    I don't understand clearly about closing/opening session here. Do you mean network connection session? If so, new session still knows about subscribed items from the old one. Now, it should know more about "receive state" of such items.

    This reminds me a sort of synchronization between the client and the LS Server where both agree on which was the last sent data.
    Yeah, that's about synchronization. That can auto make between LS client and server internally or you can provide new API at client to let developer ask server.
    Last edited by tvhnet2013; August 29th, 2013 at 03:24 AM.

 

 

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 02:29 AM.