46ec05beae
Client option rpc_response_timeout means "Seconds to wait for a response from a call"[1], but it is used by cast in zmq driver. And it's not the right way that underlying zmq driver uses an upper client option. So rpc_response_timeout should not be used in zmq driver, and let's just remove it since rpc client has passed the parameter[2]. ref: [1]: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/client.py#L37 [2]: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/client.py#L150 Change-Id: I86fe4d1f18faf8d4af666301b00e5907dce4417b |
||
---|---|---|
doc/source | ||
etc | ||
oslo_messaging | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup-test-env-pika.sh | ||
setup-test-env-qpid.sh | ||
setup-test-env-rabbit.sh | ||
setup-test-env-zmq.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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