On 05/19/2014 06:57 PM, Rafael Schloming wrote:
That doesn't require the same kind of synchronization, it just requires that the client implementation doesn't internally reorder execution of the given API requests.
If the subscription and the request are sent on the same connection and are guaranteed to be written to the wire in the order in which the API calls are made, then you are right, that would normally be sufficient (unless the broker in use can process different sessions in parallel, in which case they would need to be sent on the same session as well).
If the request is for any reason on a different connection, or otherwise 'out-of-band', then you don't have that guarantee.
To be clear, I'm not arguing for any change. I was just pointing out that subscribe() can be tracked through the current message tracker state.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
