Re: [zeromq-dev] shutting down proxy device cleanly with pyzmq

2013-10-22 Thread Sideropoulos, Alexander
at 9:46 PM, Sideropoulos, Alexander alexan...@thequery.net wrote: 13.1.0 I have attached an interactive session log which shows the issue as clearly as possible. I might just be doing something dumb, though... Thanks for looking into it. --ap On Wed, Oct 16, 2013 at 12:52 AM, MinRK

Re: [zeromq-dev] shutting down proxy device cleanly with pyzmq

2013-10-18 Thread Sideropoulos, Alexander
13.1.0 I have attached an interactive session log which shows the issue as clearly as possible. I might just be doing something dumb, though... Thanks for looking into it. --ap On Wed, Oct 16, 2013 at 12:52 AM, MinRK benjami...@gmail.com wrote: What version of pyzmq? Can you provide a

[zeromq-dev] shutting down proxy device cleanly with pyzmq

2013-10-15 Thread Sideropoulos, Alexander
I cannot seem to understand the proper use (read: shutting down) of a ZeroMQ proxy/device in Python. For example, once a ThreadProxy has been start()'ed, how does one successfully join() to it? The thread has to actually want to exit for the join() to ever return, right? My current approach is

Re: [zeromq-dev] is this allowed?

2012-09-19 Thread Sideropoulos, Alexander
There are examples in the Guide where a zmq_msg_t is received and then the same variable is later used in a zmq_msg_send() call. So I assume this usage is acceptable (assuming no differences in behaviour to the version you are using). obvious things to check: - be careful to not muck around with