[zeromq-dev] publisher side filtering
elukie at comcast.net
Wed Jun 30 14:24:17 CEST 2010
> 0MQ does not provide publishers with the knowledge of what clients
> connect. This is a weakness we need to work on.
> But if you imagine a multicast network you understand why. Clients
> connect to a switch, not to the publisher. There is thus no way by
> default to selectively publish. Thus, clients receive everything and
> filter at their edge.
> A TCP unicast network can of course do it differently but 0MQ is
> designed to work as far as possible with any transport and the
> multicast model has influenced the design of its pubsub sockets.
Yes, I see why 0MQ does what it does.
Can I build up my own pub/sub system with a set of more basic 0MQ TCP
More information about the zeromq-dev