-
March 11th, 2009, 10:26 AM
#2
Hi Shreyas,
If you want to take benefit of the highly efficient delivery mechanisms of Lightstreamer (such as delta delivery and message conflation), you should map any data model you have to a table-based data model. So, in this case, it is up to you to find the right mapping.
On the other hand, if you don't need optimized delivery, you can use opaque data types. In other words, you can serialize your complex data object into a string (through JSON, XML, or any other technique) and push it as a single field. Your client-side code will do the opposite operation, deserializing the string and getting a full-blown object again.
Again, consider that by using opaque data types, you actually hide the data model to Lightstreamer, which cannot parse the messages to extract the deltas. So, each message will be delivered "as is" to the client (thus consuming more bandwidth, also due to the overhead of the serialization syntax).
Regards,
Alessandro
Similar Threads
-
By Pradeep Chahal in forum Adapter SDKs
Replies: 1
Last Post: March 11th, 2010, 03:53 PM
-
By huynhdt in forum Client SDKs
Replies: 0
Last Post: March 8th, 2010, 10:27 AM
-
By chuan_ckc in forum General
Replies: 4
Last Post: August 14th, 2009, 03:28 AM
-
By churrusco in forum General
Replies: 10
Last Post: May 8th, 2007, 02:04 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 01:50 PM.
Bookmarks