[zeromq-dev] Broadcasting Requests
fabien.ninoles at ubisoft.com
Thu May 5 18:41:04 CEST 2011
Don't forget that it must be able to associate with an ROUTER socket to work correctly.
As a new socket, not so sure for GATEWAY. Isn't a gateway something that allow access to something else which you shouldn't access normally ? Not in my use case anyway. CARRIER or a DISTRIBUTOR may be ? The fact is a two-way sockets make it quite difficult to find the right term. COLLECTOR could be interesting too (like the ones that send you bills and expected you to reply quickly...)
How hard should it be to implement such thing ?
De : zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-bounces at lists.zeromq.org] De la part de Pieter Hintjens
Envoyé : 5 mai 2011 11:15
À : ZeroMQ development list
Objet : Re: [zeromq-dev] Broadcasting Requests
On Thu, May 5, 2011 at 4:54 PM, Fabien Ninoles
<fabien.ninoles at ubisoft.com> wrote:
> Moreover, since the behaviour of the PUBSUB/SUBPUB pair is exactly the same as an XREQ/XREP pair with simply the XREQ broadcasting the message instead of load-balancing it, I would like to know if there is feasible to have something resembling this in the future ?
If you chart the current socket types and their semantics you see that
a bidirectional fanout socket type is missing. I think you're the
first person to define a use case for it. Nice!
It doesn't make sense to implement as a socket option on an existing
socket, because this is either PUB tweaked to allow receiving, or
DEALER tweaked to broadcast instead of load-balancing. I'd suggest a
new socket type, e.g. GATEWAY.
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
More information about the zeromq-dev