[openstack-dev] blueprint amqp-rpc-fast-reply-queue
eric at cloudscaling.com
Wed Jan 30 01:25:37 UTC 2013
> With my change and compatibility mode enabled, all requests are sent in the old message format and replies listened for on the old queue. If the call is sent to Folsom, it will come back on the old queue. If the call is sent to Grizzly(fast) or Havana, those versions will recognize the old message format and reply on the old queue. So Grizzly won't have to do listen on both to be able to communicate in all the ways you say the dual queue listen approach can.
> If Folsom calls Grizzly(compat), Grizzly(compat) will recognize the old format and respond on the old queue. If Grizzly(fast) or Havana calls Grizzly(compat), Grizzly(compate) will recognize the new format and respond on the new queue.
> What else is needed? How is that any less functional than the dual queue approach?
Sorry, I didn't understand the patch to work this way. This seems reasonable.
More information about the OpenStack-dev