ffrenchm wrote:
I'm currently working on a JMS client. I suppose that the equivalent of C++ async session is a DUPS_OK_ACKNOWLEDGE session (I'm not sure) ...
Not really; DUPS_OK_ACKNOWLEDGE just controls the frequency with which messages received by the client are acknowledged (allowing the broker to dequeue them).
The async session in the C++ client means that all the commands invoked on the session interface will return without waiting for the broker to confirm that the command was processed (indeed it may well not even have yet received the command). The client can then explicitly sync() at any given point (or periodically flush() to request that the broker send information about which commands it has completed, or wait for completion etc).
There is a configuration option in the JMS client (sync_persistence = true) to require that the send() method blocks for durable messages (required for strict compliance with JMS, but obviously much slower).
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
