[zeromq-dev] zeromq & pylons

Eric Bell eric at ericjbell.com
Tue Aug 3 21:43:13 CEST 2010

I am developing an application using pylons and I am concerned about the
implications of something I read in Pieter's user guide (thanks for that,
btw, the explanation of how bind/connect is used to define the topology was
very helpful)

THE QUOTE: "You MUST NOT share sockets between threads. ØMQ will in some
future make it possible to move sockets to different threads. Right now the
thread which creates a socket is the only thread that may use it."

I am new to both pylons and zeromq, so I have a lot of murkiness about how
all this works. I imagine that pylons "handlers" come from some sort of
thread pool, but honestly I have no real idea what's happening under the
hood. In my initial design, I create zeromq sockets and store them in the
app_global object. My thinking was that then any handler "thread" could have
access to the sockets. Upon reading the quote above I am now concerned that
I have violated a basic restriction on how to use ZeroMQ sockets.

It works right now but maybe I just haven't loaded my server enough to cause
it to break. 

I welcome any thoughts or suggestions. Thanks,


More information about the zeromq-dev mailing list