Hi, First of all, the correlation_id is needed for tracking the response for callback queue per client. What you said is the inefficiency of callback queue per request. In any case, callback queue is needed.
About oslo_messaging, you can see the correlation_id in the driver of amqp. Br, Tuan/Nokia On Thu, Jun 8, 2017 at 4:29 AM, int32bit <[email protected]> wrote: > Hi, > > Currently, I find our RPC client always need create a new callback queue > for every call requests to track the reply belongs, at least in Newton. > That's pretty inefficient and lead to poor performance. I also find some > RPC implementations no need to create a new queue, they track the request > and response by correlation id in message header(rabbitmq well supports, > not sure is it AMQP standard?). The rabbitmq official document provide a > simple demo, see [1]. > > So I am confused that why our oslo.messaging doesn't use this way > to optimize RPC performance. Is it for any consideration or do I miss > some potential cases? > > Thanks for any reply and discussion! > > > [1] https://www.rabbitmq.com/tutorials/tutorial-six-python.html. > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
