Ok I understand your answer, but it raise me another question :) Is there a way to have a really asynchronous client/server communication when putting messages ? I mean the client send a message and then the server ack the client without waiting that the message is on the disk ?
Thanks ... Carl Trieloff wrote: > > >> Well, I do not understand why the synchronous IO mode is no longer >> supported. My experiences of queueing tell me that if you want really >> safe >> message store you need synchronous IO on message PUT. But maybe did I >> miss >> some new things which make this feature deprecated ? >> >> > > This is a great question: > > The key is that the C++ broker is that it is an async process, so the > broker has all the logic to know when all the async processing on a > message is complete. So even with a async store, the broker will not ack > the client until the message/update is physically written to disk. Given > this there is no advantage to a sync mode. Async is faster in all cases > - and all the exact same message guarantees are provided using async. > > The only reason the sync option was there was to enable testing while > the async impl was been hardened. > > regards > Carl. > > > > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > > -- View this message in context: http://n2.nabble.com/QPID-C%2B%2B-Broker-%2B-persistent-store-tp2372671p2372992.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
