It's all in the guide Girish: http://zguide.zeromq.org/page:all#A-Publish-Subscribe-Proxy-Server
Have the forwarder bind on both sides and the pubs and subs connect to it. -Michel On Wed, Aug 22, 2012 at 5:24 AM, girish kumar <[email protected]> wrote: > Thanks for your reply. > > Can you give more details of how multi-threaded publisher and subscriber > works. I am new to zero MQ and I feel difficulty in understanding your > solution. > > "Bind the side that has the least less dynamic IP addresses, connect > the others to them. If you really have a cloud of pubs and subs all > dynamically coming and going, use a device in the middle (forwarder) > with a known IP address." > > If any pre-material needed in understanding this solution, that will be > helpful. > > > On 22 August 2012 12:47, girish kumar <[email protected]> wrote: >> >> Hi All, >> >> We have started recently working on zero MQ. We could able to run the >> sample applications successfully. >> >> We have two problems, which we are facing issues in getting answers. >> >> 1. We have a scenario where there are multiple publishers(threads) and >> multiple subscribers(threads). We are not able to understand a model in zero >> MQ, that works for this scenario. >> - As zero MQ sockets are not thread safe, can we make zero MQ sockets >> threadsafe by applying explicit locks?. >> >> 2. Another problem is we are running some performance tests for best >> results. We would like to know the highest possible numbers(latency and >> throughput) achieved with zero MQ. >> >> Any help in this regard is highly appreciated. >> >> >> -- >> With Best Regards, >> Girish >> > > > > -- > With Best Regards, > Girish > > > _______________________________________________ > 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
