wwatts
We are integrating Lightstreamer with a thick application that has the need to be subscribed to multiple tables of data. For example a given window may have up to 3 different types of data that needs to be updated. Using the .NET client API do you create three connections (OpenConnection calls)? We also have the need to unsubscribe and subscribe to different tables (the tables may or may not be contained in the same Data Adapter) as the user navigates through the application. How would this be accomplished? To give you some background, I have used the web client API and what we would like to do is create a master page and have child push pages reference the master page. Each child push page would subscribe to data on load and unsubscribe on unload. How would a similar situation be handled for a thick application using the .NET API?
Alessandro Alinone
With the .NET Client you have the same capabilities of the Web Client to subscribe and unsubscribe to/from tables (possibly coming from different Data Adapters) as part of the same sessions ans using the same connection.
You will simply call SubscribeTable() and unsubscribeTable() on the LSClient object at any time.
wwatts
Thanks for the quick answer. I thought that was the case but wanted to confirm.
AidasOzelis
Which one is better: a connection per each subscription or a connection per client application (one connection for all subscriptions)?
Mone
the best way to go is one connection per client. The library will take care of dispatching the received updates to the correct listener.
