[zeromq-dev] publisher side filtering

Matt Weinstein matt_weinstein at yahoo.com
Wed Jun 30 15:46:12 CEST 2010


Thoughts:

Data coloring: Publish on multiple ports, one for each type of data.

Crypto: Multicast can go anywhere. If you really have a security  
issue, you could encrypt the payload and use REQ-REP to get the  
current keys (and age them out)

On Jun 30, 2010, at 8:24 AM, ernie wrote:

> Pieter,
>
>> 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
> patterns?
>
> Ernie
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev




More information about the zeromq-dev mailing list