5d7d7253d1
Current Listener interface has poll() method which return messages To use it we need have poller thread which is located in MessageHandlerServer But my investigations of existing driver's code shows that some implemetations have its own thread inside for processing connection event loop. This event loop received messages and store in queue object. And then our poller's thread reads this queue This situation can be improved. we can remove poller's thread, remove queue object and just call on_message server's callback from connection eventloop thread This path provide posibility to do this for one of drivers and leave as is other drivers Change-Id: I3e3d4369d8fdadcecf079d10af58b1e4f5616047 |
||
---|---|---|
.. | ||
drivers | ||
functional | ||
notify | ||
rpc | ||
__init__.py | ||
test_amqp_driver.py | ||
test_exception_serialization.py | ||
test_expected_exceptions.py | ||
test_fixture.py | ||
test_opts.py | ||
test_serializer.py | ||
test_target.py | ||
test_transport.py | ||
test_urls.py | ||
test_utils.py | ||
utils.py |