Hi Giacomo, I'm happy to hear you choose netmq, answers to your questions:
1. There are no functionality differences between NetMQ and CLRZMQ/ZeroMQ, there are some small API differences between NetMQ and CLRZMQ. 2. Same as ZeroMQ, so publisher side (it's based on ZeroMQ 3.2.2) 3. What to do you mean blocked? how did you noted that? I don't think you should queue because NetMQ / ZeroMQ is already doing exactly that. Just consume the messages from the socket. Doron On Thu, Jun 27, 2013 at 1:04 AM, Giacomo Tesio <[email protected]> wrote: > Hello everybody, I'm working to my first ZeroMQ based real-world > application and I have a few questions: > > 1) I'm working on .NET and I choosed NetMQ instead of CLRZMQ just on the > base of github activity. I've noted there are some differences between the > two API (for example I had to Subscribe("") instead of SubscribeAll()) but > they seem minor differences at a first look. Is there any difference in > functionality that I should be aware of? > 2) I have to use a topic based PUB tcp socket: is PUB/SUB filtering done > at publisher side? > 3) I noted (in debug) that the publisher blocks while the subscribers > handle each message: I've tried to minimize the impact of this with a queue > of messages of subscriber side, with the subscriber that fills the queue > and another thread consuming it. Is there a better approach? > > Thanks a lot! > > > Giacomo > > _______________________________________________ > 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
