Hi Ernie, ZeroMQ does not directly support this, you would build it as an application on top, defining your own protocol to connect clients and server.
I'm designing something that looks a bit like this, with peer-to-peer message flow, and rough-grained security based on "streams" of data rather than a topic tree. It needs to work over multicast, meaning that you can't apply access controls at the server side. -Pieter On Wed, Jun 30, 2010 at 2:54 AM, ernie <[email protected]> wrote: > I am looking at building a message dispatch system. The clients connect > to a server on a well known port and subscribe to 'topics'. Clients can > also generate 'topics' of their own which are published to other > subscribed clients. > > I need the subscription filtering to be done on the server rather than > the individual clients. One reason is "psuedo-security" -- some of the > 'topics' I do not want to be pushed to certain clients. Another reason > is the 'topic' subscriptions will be sparse -- only a few of the main > clients will be subscribing to individual 'topics'. > > Looking at the message patterns available in zeroMQ, I'm not clear that > I can accomplish this. I need to be able to identify which client > generated a message and route it to subscribed clients. I can not do > this with the pub/sub pattern. Since there is no response, I do not see > that I can use the req/rep pattern. I am new to zeromq, so I figure I > am not understanding how or if I can implement this. Any suggestions > would be appreciated. > > _______________________________________________ > 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
