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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev