I'm not big fan of this as well. I think you can implement it in a layer above zeromq. However if it useful for you just send a pull request.
One note though, sending a Msg to multiple pipes is complicated and you need to manage reference counting. Take a look at xpub and dist classes for example. On Fri, Jun 17, 2016 at 10:06 PM, Justin Karneges <[email protected]> wrote: > Hey Jens, > > My initial thought is that this doesn't feel right. You'd be limited to > broadcast (making it a kind of substandard PUB), and you'd need to change > the "mute state" behavior too (otherwise a single slow client triggers > EAGAIN). > > On Fri, Jun 17, 2016, at 10:09 AM, Jens Auer wrote: > > Hi, > > > > I am using ZMQ_STREAM to receive and deliver data from/to non-zeroMQ > applications. For delivery, I have to send the data to a number of > connected clients. All clients receive a copy of the data. Since a > ZMQ_STREAM socket needs a first peer identity part, I have to manually add > this every time I send a data message, and keep track of connected client > ids. I think it would be nice if ZMQ_STREAM could do this internally. I > think this could be done by allowing empty peer ids which are then > interpreted as “broadcast”. Any thoughts on this? > > > > Best wishes, > > Jens > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virenfrei. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > *_______________________________________________* > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
