OpenStack library for messaging
aebe53f242
Concurrency. Sigh. A sequence of events like this is possible: - We send a request from thread A - Thread B, who is waiting for a response gets scheduled - Thread B receives our response and queues it up - Thread B receives its own response and drops the connection lock - Thread A grabs the connection lock and wait for a response to arrive The obvious solution is that when we grab the connection lock, we should check whether a previous lock-holding thread had already received our response and queued it up. Change-Id: I88b0d55d5a40814a84d82ed4f42d5ba85d2ef7e0 |
||
---|---|---|
doc/source | ||
oslo | ||
tests | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messsaging transports.