75cba16d15
At the moment for each msg_id we receive two amqp message - first one with the payload, a second one to ensure the other have finish to send the payload. This was made, because a long time ago 'reply' allowed generator as payload to send multiple messages on one 'rpc.call' - [1] It's a bad idea - to double RPC messages for each call, so we are going to remove this the second AMQP message sending. This patch allows receiver side to proceed correctly old case - two AMQP messages (first with data and second with 'ending' parameter) same as the new one (a single message with data 'ending' parameter) Blueprint: remove-double-reply [1] - https://github.com/openstack/oslo-incubator/blob/stable/icehouse/openstack/common/rpc/amqp.py#L464 Change-Id: Ic09fe619694c300c4502acb7157d7ecdd47c5fd7
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
- License: Apache License, Version 2.0
- Documentation: http://docs.openstack.org/developer/oslo.messaging
- Source: http://git.openstack.org/cgit/openstack/oslo.messaging
- Bugs: http://bugs.launchpad.net/oslo.messaging