A while back I ran into this same issue; my solution was to have the client
transmit an identifier (in my case, the public IP) when it first connects.
Annoying that this isn't possible (to my knowledge) using only ZMQ APIs,
but not the end of the world.
-E
On Thu, Sep 25, 2014 at 7:46 AM, Scott w
Hello there, I'm trying to figure out the proper way to read a message
whose size I do not know from a socket. Is there a way I can "peek" at the
size of the next message part to be received in ZMQ? I'm using ZMQ 4.0.
Thanks!
-E
___
zeromq-dev mailing li
To answer this, I realized I had completely overlooked the zmq_msg_t based
interface, which obviates the need to know the size of the message before
receiving it. Pardon the noise.
-E
On Fri, Jul 24, 2015 at 6:11 PM, Elliot Saba wrote:
> Hello there, I'm trying to figure out the prope
vious
versions; is this a feature that hasn't been implemented yet, or am I
grabbing the wrong code?
Thank you very much,
-Elliot Saba
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Thanks Martin.
I'm currently developing a networked filesystem, and I'm using zmq as my
transport layer for both in-process concurrency management and external
peer-to-peer communication. The peer-to-peer communication includes both
freeform peer-to-peer communication and structured large-scale
s
Thanks for the link to the planning article, Pieter. I think I will
continue to use zmq 3.0 for now, and port to 4.0 if I run into problems.
-E
On Wed, Aug 31, 2011 at 2:55 PM, Pieter Hintjens wrote:
> On Wed, Aug 31, 2011 at 11:45 PM, Elliot Saba
> wrote:
>
> > I'm not ye
Hello, Marc, in addition, I suggest you read up on the SO_REUSEADDR (On
linux, there is also a SO_REUSEPORT option, but SO_REUSEADDR should do the
same thing on windows) socket option, and if that looks like your problem,
maybe try modifying the sources to use that option when creating a socket.
-E
Hello, I'm trying to use a ROUTER socket to communicate to a new peer that I
have not received any messages from before. I know that to use a ROUTER
socket to speak with this peer, I should prepend the peer's identity in a
separate message part, but I have no way of knowing what identity this peer
Hey Martin, for some reason it's not working for me. My messages appear to
be dropped by the ROUTER socket before leaving the interface.
Does the introduction of the LABEL flag have anything to do with this?
Right now I am sending the "address" of the peer I wish to talk to with
just a ZMQ_SNDMO
I have created a small test case that produces this error, please see the
JIRA issue.
It occurs when I create a ROUTER socket, send a message, then disconnect,
many many times over again.
-E
On Fri, Sep 30, 2011 at 6:47 PM, Mikko Koppanen wrote:
> On Fri, Sep 30, 2011 at 11:22 PM, Zed Shaw wrot
Alright, so I have a ROUTER <-> ROUTER setup working by having each ROUTER
socket set its identity to its own external IP address/port combination
(e.g. "tcp://1.2.34.56:7890"). This allows each ROUTER to predict the
identity of each other ROUTER, (otherwise I would never be able to send
messages
I second this notion, it allows for much more graceful error handling, even
in the case of errors that "should never happen". This makes the error
checking the asserts do much more meaningful for users, and not just
meaningful for zmq developers.
-E
On Sun, Oct 2, 2011 at 11:04 AM, Ian Barber wr
If I may chime in here, my biggest problem with the identities concept, is
that there is no way to have a ROUTER connect to a socket, and then know how
to talk to that socket. Identities are exchanged by the underlying zmq
transport layer on successful connection I believe, but the user has no way
011 at 3:35 PM, MinRK wrote:
>
>
> On Sat, Oct 29, 2011 at 13:49, Elliot Saba wrote:
>
>> If I may chime in here, my biggest problem with the identities concept, is
>> that there is no way to have a ROUTER connect to a socket, and then know how
>> to talk to that
Hello, I have a small variation on a problem that I've seen talked about
before, (and I have brought up before) but I've never found a good solution;
Let's imagine I'm programming something akin to the Bittorrent network; I
have trackers and peers, and the ip/port addresses of which I do not
initi
15 matches
Mail list logo
