On Wed, 2016-03-16 at 20:16 +0000, Gordon Sim wrote: > On 16/03/16 15:51, Flores, Paul A. wrote: > > > > The discussion has focused on the following: > > > > path 1: use request/reply "framework" with requester explicitly > > listening for the reply, blocking processing until reply has been > > received. > This pattern is used a lot (including in all the management tools > for > the c++ broker). > > > > > path 2: using direct receive (i.e. proton example) accepting > > message only after processing has been completed. > If I understand correctly, the idea here is to use message > acknowledgement instead of an explicit reply message? If so, that > only > really works where the reply has no content
It also doesn't work if messages are queued on a broker or some other intermediary since you'll get acknowledgement from the broker before the real server has seen the message. It can work in a direct peer-peer communication but path 1 is more robust. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
