Hmm, I think you can attach just one monitor to libzmq, period. What you can certainly do then is re-send monitor events to other parts of an application.
On Sat, Oct 18, 2014 at 9:50 AM, cbisegni <[email protected]> wrote: > Is possible to have only one monitor for more socket? When I have studied > how to use monitor socket all example and test that i have done, have worked > using one monitor for one socket. Image if I have a process that need to > manage a lot of connection and check when client goes away and I have to > dispose the socket for clean resource. I need a socket for every client > because every connection manage different data(so I can't use the same > socket with different endpoint). > Using one monitor socket on a separate thread for every client socket > connection(this is example that I have found), is not the best situation on > an high number of client. How can zmq be used to manage this situation in > the best way? > Thanks in advance? > Best regards > Claudio > > il 18/ott/2014 00:26, Pieter Hintjens <[email protected]> ha scritto: > > It's called zmonitor, and works as an actor. > > -Pieter > > On Fri, Oct 17, 2014 at 10:36 PM, Papp Aron <[email protected]> wrote: >> Hi, >> >> I'm using CZMQ 3.0.0 (libzmq 4.1.0), and trying to leave the deprecated >> zsocket, and move to zsock. Previously, I used zmonitor to check if the >> TCP >> connection was established successfully, but I can not find it's >> substitue, >> zsock_monitor. >> >> Is there another way to check connection state? >> >> Best regards, >> Aron >> >> _______________________________________________ >> 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 _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
