The code is very simple with a single INPROC forwarder within process and a TCP Forwarder to talk to the other node. I am also adding ZooKeeper to discover and connect and configure the nodes. I am getting CPU utilization that is just nuts, though, I would love to be able to be able to halt the thread that does not have any messages for it, it is that I need to be able to let it know that the client it is servicing is gone and it should shut down. Java is discouraging the use of Thread.Stop().
Mike. On Feb 16, 2011, at 12:21 PM, Pieter Hintjens wrote: > On Wed, Feb 16, 2011 at 9:16 PM, Michael Kogan > <[email protected]> wrote: > >> It seems that my thread-per-user approach is not something that others are >> doing. I imagine they are using polling instead. > > Threads are pretty cheap and it can be very elegant to use a thread > per socket. It depends how much management you need on top of the > socket set. > > So it's definitely a valid design pattern for 0MQ. > > -Pieter > _______________________________________________ > 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
