When a DEALER sends a message with one frame to a ROUTER, the ROUTER
will deliver two frames; the identity, then the message. This is the
same on 2.2 and 3.2 and 4.0.
Your test code sends Hello without a training null byte and then
tries to print the string. It also tries to print the identity
Hello,
I was wondering if it was possible to somehow retrieve the IP and port
from a connecting client in libzmq/czmq?
thanks
Mathias
pgpjFWjjHLkvE.pgp
Description: PGP signature
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
I have a networking application that I'd like to use ZeroMQ in. However, my
use-case demands minimum latency even at the expense of lost messages. I'm
weary of using ZeroMQ's TCP transport because if packets are dropped, TCP
will block further messages until it has retransmitted the last one, and
Hi Lindley,
The right solution would be to make a UDP transport for ZeroMQ. It's
not a trivial project but could start with, for instance, just pub/sub
(like PGM).
It might be worth looking at Crossroads.io for that, which is
abandoned but had afair a UDP transport, and shared the same original
I also cut pyzmq-14.0.1 yesterday, which bundles 4.0.3.
On Sun, Nov 24, 2013 at 11:50 PM, Pieter Hintjens p...@imatix.com wrote:
Hi all,
There was a failing test case in 4.0.2 (error in a new test case, not
the library), so we made a 4.0.3 release to fix that. Same place as
usual. Sorry
Hi, Pieter
Thanks for your immediate reply...I know that there are two frame
which ROUTER would receive when DEALER peer send a message to ROUTER, the
first frame is identity, and the second frame is my sent content..but I
find that if the message sent from zeromq4.0.3 to zeromq2.2, two
