Hi folks,
I am new to zmq/czmq and zyre. Please pardon me if these questions are too
basic.
I am trying to use zyre for inter-thread communication and discovery of
nodes. Each thread doesn't have the prior knowledge of which thread it
needs to communicate to. So instead of maintaining my own
On Sun, Feb 8, 2015 at 12:53 AM, MinRK benjami...@gmail.com wrote:
I guess the problems I identified that it solves weren't really problems,
then.
Where in the email below are you identifying the problems that the
experimental split of multipart messages into labels + parts was
trying to
Hi Kalyan,
For inter-thread communication you can use zyre with its gossip
discovery. There's an example in zyre_test ().
Every message (ENTER, SHOUT, WHISPER) has the UUID address of the
sender. You can use this to WHISPER back to it.
Typically if you want to identify nodes in other ways you
On Sun, Feb 8, 2015 at 1:14 AM, Pieter Hintjens p...@imatix.com wrote:
On Sun, Feb 8, 2015 at 12:53 AM, MinRK benjami...@gmail.com wrote:
I guess the problems I identified that it solves weren't really problems,
then.
Where in the email below are you identifying the problems that the
This is actually what I'm hoping to extend Zyre with. As nodes running
on the same machine are better off using a different transport than tcp.
But having multiple paths to nodes implies the need for some priority
thing.
Rg,
Arnaud
On 2015-02-08 11:13, Pieter Hintjens wrote:
Hi Kalyan,
On Sun, Feb 8, 2015 at 8:32 PM, Kalyan Bade kalyanb...@gmail.com wrote:
Regarding the UUID for whisper message, it looks like that I have to cache
the name to UUID mapping in my application.
Since names aren't unique they can't really be used as addresses.
There may be other ways of doing
Hi Pieter,
Thanks a lot for the answers. Please see inline..
For inter-thread communication you can use zyre with its gossip
discovery. There's an example in zyre_test ().
I was using gossip hub for discovery and the discovery is working.
Every message (ENTER, SHOUT, WHISPER) has the
This ties into the heart of some related discussions we've been having
at work recently. We have a bunch of new hires who are trying to come
to grips with a messaging protocol that's evolved over the past year
or so as we've gotten more familiar with 0mq and adapted it to our
changing needs.
It's
Just in-case you misread the title, this post is about pyczmq not pyzmq.
This is just a FYI so that at least the list is aware. The last pyczmq
commit was about 7 months ago. Obviously this is not impacting many people.
pyczmq appears to be broken even though the Travis badge indicates a
passing
