At a client site.  Incorporating QPID as a solution to their messaging 
requirements.  One of the existing requirements is to support a small set of 
synchronous processes.



Team has been in discussion if using the direct receive and/or send can satisfy 
this requirement.



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.

path 2: using direct receive (i.e. proton example) accepting message only after 
processing has been completed.



Are there other "paths" to consider?



Is anyone using either of these "paths" for synchronous processing?



Insights, inputs and comments welcomed!



Regards,



Paul

Reply via email to