-
January 14th, 2010, 03:31 PM
#1
Admittedly, there was a change, but it was considered as an internal change with no practical effects. Now, your case exploits the difference.
To resume, the table clearing associated with an addTable invocation, in case the Engine were currently disconnected, was deferred until the first connection.
With Server-originated updates nothing has changed. Even in case of reuse of the same table with removeTable + addTable, you can cause the old table contents to be cleared as early as possible through setClearOnRemove, whereas, through setClearOnAdd, you can cause the old table contents to be cleared as late as possible.
However, your showValues occur after addTable and before the connection takes place and this now causes them to be cleared. Only performing the calls upon onStart would work.
We acknowledge that your use of showValues makes sense and will try to restore the original behavior. Sorry for the inconvenience.
-
February 17th, 2010, 04:21 PM
#2
Hi Andreas,
The new release has been issued, but the discussed change couldn't be included,
as it was deferred until a thorough refactoring of the topic is finally performed.
If you are still bound to this change, we can provide you with a private update, when available.
-
February 18th, 2010, 11:14 PM
#3
Hey Dario,
thanks for the update, I'll keep it in mind - seeing as the new release promises quite a lot of optimizations (both on the server and on the client side) I'd really like to deploy and use it as quickly as possible, so I'll check with the project in question if we can implement the call to "showValues()" in the "onStart()"-event for the time being. Nevertheless, I'd really appreciate it if you could give me an update when you've had the time to refactor the functionality, so we have a chance to evaluate the updated version.
By the way, congratulations to the new version! Just read through the release eMail and had a quick look over the detailed release notes - sounds really interesting, and I really like that you've added the option to keep the global Javascript namespace "clean" by grouping all the Lightstreamer functionality within the "Lightstreamer" namespace (by calling avoidLSGlobals).
Cheers,
Andreas
Similar Threads
-
By Mone in forum Client SDKs
Replies: 1
Last Post: July 10th, 2012, 06:06 PM
-
By enrico in forum Client SDKs
Replies: 2
Last Post: March 1st, 2012, 01:53 PM
-
By RichPratt in forum Adapter SDKs
Replies: 7
Last Post: June 7th, 2010, 09:38 AM
-
By hofmanna in forum Client SDKs
Replies: 5
Last Post: January 14th, 2010, 10:02 AM
-
By jondcruz in forum General
Replies: 1
Last Post: September 18th, 2009, 09:13 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 11:17 AM.
Bookmarks