Hi,
Since I'm new to ZeroMQ I really appologize if my question is stupid, but
can we use a Router to broadcast messages to all clients ?
I mean, I don't see any technical reason it couldn't, and I know I also
could create Request/Req and Pub/Sub sockets for instance, but I don't want
to create
Hello All,
I need some suggestion on my design and ways in which it can be done using
ZMQ sockets.
I have an app App1 on Box1. It sends a message M1 (128K) to an app App2 on
Box2. App2 will do some processing on M1 before sending an ACK back. In my
application, I also want to send an ACK back
unless you're not telling us something,
the simplest solution is two sockets:
app1.PUSH = app2.PULL: for M1
app2.PUSH = app1.PULL: for various ACKs
as for the matching, i would include an job id with M1 and the ACKs.
or if you don't want to do that, use the system name (Box2) as the id.
both
You technically could if
you kept track of all the addresses that you received. The main downside
is that you don't know when someone connects/disconnects. You only know
what requests were received.
Joshua
Grgoire Passault
Thursday, July
12, 2012 9:43 AM
Hi,Since I'm
Of course ...
But think of an hybrid Router-and-Pub socket, users could subscribe to
broadcast or exchange adressed data in the same socket. Why not?
Greg
Le 13 juil. 2012 00:54, Joshua Foster jhaw...@gmail.com a écrit :
___
zeromq-dev mailing list
Anything is possible :)
There was some experimentation going on the 3.0 version that created a
Generic socket. Your hybrid socket could be developed with it because
you would get the Connect/Disconnect information.
Joshua
Grgoire Passault
Thursday, July
12, 2012 6:57 PM
Thanks guys,
Unfortunately there is no python stack trace, it looks like the error is
coming from a zeromq thread and then sending the SIGABRT up. I don't know
where the conflict is coming from though. I guess I need a better
understanding of some of the threading that zeromq is doing underneath
