[zeromq-dev] Windows and PGM

Jon Dyte jon at totient.co.uk
Sun Mar 28 12:06:52 CEST 2010

gonzalo diethelm wrote:
>>> Maybe starting with zmq_device call that would do the loop and never
>> exit
>>> would be the easiest. It's ugly and won't work for python, but at
> least
>> it
>>> would further the issue a bit.
>> Yes, this makes sense.  Once it is working, it won't be too difficult
>> to put the device event loop into a thread and provide a start/stop
>> API.
> One thing I am doing now is to add an inproc socket to all of the "real
> work" sockets I am using. The separate socket polling thread also polls
> for this inproc socket and reads "commands" from it: pause, continue,
> stop. I am sending a single char (P, C, S) in each case. This could also
> become a standard way of making this loop stop whenever needed.
> Note: pause / continue are useful to me because I must read data from a
> DB and make sure that data has been read before I start processing
> messages. 0MQ's inproc sockets make this thread synchronization easy and
> inexpensive.
I've been thinking along similar lines :-

every 'device' could contain an inproc 'control' socket for control 
messages such as


More information about the zeromq-dev mailing list