Open Stack

Also, why are you spawning a greenthread when sending a cast ?  
We need to create a socket and send to it. These are blocking operations. They're generally fast, but they are blocking. The idea was to let these loose in a greenthread as quickly as possible. This could be done higher in the abstraction.
One thing I'm thinking about after seeing this "real" driver is that  
whatever I/O framework you're using, you'll have one thread/coroutine  
that's a server pulling off messages and dispatching them and other  
threads/coroutines blocked in call() waiting to pull its reply off the  
queue. I think that's what we're doing now with eventlet and the kombu  
and qpid drivers at least, but I'm not sure yet there aren't nasty  
issues implied for other drivers or I/O frameworks.  
With the ZeroMQ driver, "consume_in_thread" is actually, "consume in threads". It spawns multiple coroutines.


Regards,

Eric Windisch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130607/f9f46a50/attachment.html>