the peer.
ROUTER pipes are created only for known identities, i.e. for a peer
that has sent us its identity, no matter who connected to whom.
We could force pipe creation in some way but it would require changes.
Hope this helps.
-Pieter
On Fri, Apr 5, 2013 at 11:13 PM, Anoop Karollil
Pieter Hintjens wrote:
On Mon, Apr 1, 2013 at 6:23 PM, Anoop Karollil anoop.karol...@gmail.com wrote:
Pieter, any clue as to why the send with the connected (not bound)
ROUTER socket might be failing initially?
No clue, but if you can make a minimal test case in C, we can
investigate. Afaik
send a msg off the ZMQ_ROUTER
socket without it already had received a
msg first. In your example you send to the broker first. Also in your
loop there should be REQ-REP pattern eventually somewhere.
-Mark
On Mon, Mar 25, 2013 at 4:53 PM, Anoop Karollil
anoop.karol...@gmail.com
On 13-03-25 11:14 PM Pieter Hintjens p...@imatix.com wrote to ZeroMQ
development list zeromq-dev@lists.zeromq.org :
On Tue, Mar 26, 2013 at 12:53 AM, Anoop Karollil
anoop.karol...@gmail.com wrote:
When I try sending messages via a ROUTER socket to a ROUTER socket (both
having
On 13-03-26 11:07 AM Pieter Hintjens p...@imatix.com wrote to ZeroMQ
development list zeromq-dev@lists.zeromq.org :
* 0MQ sockets manage a set of pipes to connected peers
* A pipe is created either on a connect (at once) or when an incoming
connection arrives
* No pipe means messages can't be
Pieter Hintjens wrote:
On Tue, Mar 26, 2013 at 10:09 PM, Anoop Karollil
anoop.karol...@gmail.com wrote:
And
yes, like you said, the send after connect succeeds if there is a pause in
between.
The send should work immediately after connect, which creates a pipe
at once. It's the bind that's
Hello,
I am using ZeroMQ 3.2.2 and PyZMQ 13.0.0.
When I try sending messages via a ROUTER socket to a ROUTER socket (both
having their identities set), with ZMQ_ROUTER_MANDATORY set, the initial
send of the destination sock identity (sent before actual message for
routing) fails once, but
