Results 1 to 4 of 4
  1. #1
    Senior Member
    Join Date
    Jul 2009
    Location
    sofia
    Posts
    40

    Client receive old data after some time.

    Hi, again .
    I successfully integrated lightstreamer for one of our products, but now in the test phase, i am observing that after some time the application begin to receive "aged data", i.e. data that was received from the feed before 2-3-4 minutes. For my testing environment i am using the trial vertion of the moderato edition. So do i have to do some additional configuration in order to fix this (the docs said that LS has automatic adaptive filter streaming).

    Regards.

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    975
    It is possible that the update events queue up on the Server,
    particularly in Moderato edition, which has a predefined delivery frequency limit.
    However, it depends on the the subscription attributes.
    Which subscription mode are you using?
    If you are not using RAW mode, are you setting the frequency as "unfiltered"?

  3. #3
    Senior Member
    Join Date
    Jul 2009
    Location
    sofia
    Posts
    40
    I am using DISTINCT type.
    How do i set this frequency setting? What does this setting do?
    Regards.

  4. #4
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    975
    You can set
    myTable.setRequestedMaxFrequency("unfiltered");
    on the client page to ensure that none of the update events is filtered by the Server;
    this causes the Server to enqueue the events, if needed.

    Even if you don't use the above setting, the Server enqueues the update events rather than filtering them, as long as there is buffer space available.
    While in MERGE mode the default buffer size is 1, in DISTINCT mode it is the maximum possible.
    You can force filtering in DISTINCT mode by explicitly reducing the buffer, through
    myTable.setRequestedBufferSize(5)
    for instance.

    In Moderato edition, an upper limit of one update per second is forced on the frequency for all items,
    hence, for items with a source update frequency higher than that,
    you can't help but either filtering or enqueueing.

    If the source update frequency were steadily above one per second, then enqueueing would not be an option,
    as the buffer would fill up and you would get delayed, yet filtered, updates.
    In that case, setting a buffer size of 1 would be the only option.

 

 

Similar Threads

  1. Getting time out on initial subscription request
    By PeterHiross in forum Adapter APIs
    Replies: 4
    Last Post: December 20th, 2010, 09:36 AM
  2. Can I receive the original data?
    By Johnny in forum Client APIs
    Replies: 10
    Last Post: September 13th, 2010, 12:06 PM
  3. Replies: 3
    Last Post: March 6th, 2009, 04:13 PM
  4. Replies: 1
    Last Post: February 22nd, 2008, 09:39 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 12:48 PM.