Hello MinRK,
Thanks for the reply, now i have two more questions from your answer:
1) What do you mean b telling daemon=TRUE, does the background process run as a
infinite loop or something like that.
2) Now my code was working good in Python 2.7.2 but when i test this on python
3.x i get a
Thanks for the info.
-- Alex
On 26 March 2012 20:11, Lourens Naudé lour...@methodmissing.com wrote:
Hi Alex,
That'll be fine - the fd events are edge-triggered and would work with any
reactor implementation. Just remember to read until completion as the
notification can be for more than one
Hello all.
I solved the second error myself but i am still confused abt the first question.
From: proj_symb...@live.com
To: zeromq-dev@lists.zeromq.org
Date: Tue, 27 Mar 2012 09:03:57 +0200
Subject: Re: [zeromq-dev] FW: Help With Regard To the ZMQ Forwarder
Hello MinRK,
Thanks for the
The daemon flag, and every other aspect of the multiprocessing module
is very well documented:
http://docs.python.org/library/multiprocessing.html#multiprocessing.Process.daemon
-Michel
On Tue, Mar 27, 2012 at 4:18 AM, Ronald Swain proj_symb...@live.com wrote:
Hello all.
I solved the second
On Tue, Mar 27, 2012 at 00:03, Ronald Swain proj_symb...@live.com wrote:
Hello MinRK,
Thanks for the reply, now i have two more questions from your answer:
1) What do you mean b telling daemon=TRUE, does the background process run
as a infinite loop or something like that.
See the
Hello,
I am using the zmq java binding in my project, I can launch my main class
without any problem from Eclipse, I can make run the ./local_lat.sh in the
perf directory but when I tried to launch my main class from a jar I get a
java.lang.NoClassDefFoundError: org/zeromq/ZMQ
Let me explain
I
Michel,
Thanks for the example. However, from what I understand, this pattern does
not allow process A to re-send the request in case it has not received the
response after a certain amount of time, because REQ sockets don't allow
multiple messages?
-Andrei
You can use non-blocking ROUTER on
Hi everyone,
I'm running into a (related?) issue where after a period of being idle, the
first message I send over a PUSH socket gets lost, as in I see it going out
on the sender side, but I don't see it on the receiver side. Subsequent
messages arrive OK, so that makes me think it may be a
