Handle Different Subscription Types For the Same ItemName (DataAdapter)

[TannerR]

Hi Giuseppe,

Thanks for taking the time to reply.

I understand what you are saying, that makes sense. I think your scenario of just not listening to the unwanted fields would make sense if we had just one system providing updates on our backend. However, in our scenario, there is some additional complexity in the fact that Bid and Price updates come from different places. As such, we only want to make subscriptions to the sources on the backend if lightstreamer has clients listening to these fields on the front end. Hopefully that makes sense.


It looks like in the demo you are provided, you are essentially doing what I was suggesting? So, you are subscribing to <stock>_BUYSIDE, <stock>_SELLSIDE, etc. Both of those items get different types of updates/information for the same stock. This is essentially what I was suggesting when I mentioned doing something like "prices:1234" and "bids:1234". Different updates/info subscriptions for the same contract.

I just wanted to clarify if there was a better way to do this, but from that demo is seems like this is viable solution?

Thanks,
Tanner

[giuseppe.corti]

Hi Tanner,

Yes you are right, I confirm that in cases like yours, when the type of information is very different or the external data sources are different, splitting the information on several Items makes total sense.

Regards,
Giuseppe