21
●1 ●2 ●6
When multiple clients request same data is it possible for the interactive provider to send one message out rather than sending individual message for every stream
4.4k
●10 ●6 ●9
Hi @Kam.Anjorin
The provider must write to each connected channel.
However, when the clients connect through TREP, TREP will manage the clients and made only a single connection channel to the interactive provider. And as a result, when the interactive provider sends the message to TREP channel, TREP will fan-out the message to all clients.
If the clients connect directly to the interactive, then the provider must write to their connected channel.
Also;
Connected channel means the rsslChannel that returned when the provider accepts a connection, and should not be confuse with the "item stream".
Each connected channel could have multiple "item streams", which represent each item request-response stream; e.g. when a client request <IBM.N>, it creates stream id 1, then <JPY=> create stream id 2 etc..
If a client on a connected channel requests the same item on a different stream id, then the provider should reject that request and inform the client that the item stream already exists.
21
●1 ●2 ●6
If there are 5 clients requesting for same dataset e.g. Symbol "IBM"
Will it be possible to send 1 message to 5 clients? Or do I have to send total of 5 individual messages to 5 clients?
Hello @Kam.Anjorin, are consumers going to connect to your provider directly, each consumer establishing a separate connection, or via TREP?
21
●1 ●2 ●6
@zoya.farberov & @Christiaan Meihsl
This is interactive provider that sends mkt data (L1&L2) via adh/ads to the clients.
it is based on UPA API running Linux with TR upa8.0.0.L1.linux.rrg.
98 percent of clients connect via ADS/ADH and 2 percent connect directly to the interactive provider. The interactive provider is based on UPA API.
