bug: should we use one client per subscription ?

[EvolveArt]

Currently I observe that if using only one shared client across tokio tasks we get some weird behavior where messages are losted or wrongly routed. Is that expected behavior?

[wboayue]

The client is designed to be shared across tasks via Arc. Messages are routed by one of three mechanisms:

1. Request ID - most data requests (market data, contract details, historical data, etc.) are routed by request ID, which is unique per subscription. These work correctly when shared.
2. Order ID - order-related messages (OpenOrder, OrderStatus, ExecutionData) are routed by order ID. These also work correctly when shared.
3. Message type - a few messages without request or order IDs (e.g., ManagedAccounts, NextValidId) are broadcast to all subscribers of that type. Multiple tasks subscribing to the same type will all receive the same messages, which could cause unexpected behavior.

Could you share a minimal example showing the issue? Knowing which specific API calls you're making concurrently would help narrow down whether this is a routing issue or something else.