DataProvider slow subscribe operation

[trader-123]

Dario, I'm sorry for the late reply.

I think that's clear now! I wasn't too far from the solutions. Would you suggest using a queue instead of the data_adapter_pool solution?

Is there a recommended way for our use-case, or is this new territory for LightStreamer?

Cheers!

[DarioCrivelli]

A subscribe operation performing a HTTP call is a case that we consider, and this is why we provide the solution of the DATA pool to tackle the case in a simple way.
Enabling the DATA pool is not very different from working asynchronously through a custom queue.

From the client point of view there is no difference, because the client never waits for the completion of the subscription operation.
Slow subscribes obviously may delay the arrival of data, but this can't be avoided in both ways.
The main problem we see is when a slow subscribe causes the postponement of the execution of other subscribes, either for the same item or for other items.

On this respect, a custom queue just allows for more control.
For instance, the size of the DATA pool is preconfigured, whereas with a custom queue you can choose at any time how many subscription operations to run concurrently.
Also, with a custom queue you still have the problem of handling possible sequences like [ subscribe() - unsubscribe() - subscribe() ] for the same item;
but perhaps you may have devised a way to run such operations in parallel.

In general, we don't suggest the use of a custom queue unless the use of the DATA pool proves to be too limited.