Hi Randall, There's events support built into the recent 3.2.x releases :
http://api.zeromq.org/3-2:zmq-socket-monitor Currently there's no events bubbling up for HWM thresholds etc. On Tue, May 14, 2013 at 1:54 PM, Randall Nortman <[email protected]>wrote: > While I'm complaining about stuff missing from the current API, let me > mention this: It would be nice to be able to get at some information > about what peers are currently connected to a socket, and how close > each peer is to hitting its high water mark (i.e., how many queued > messages). It would also be nice to get connect/disconnect and > muted/unmuted notifications somehow. These could be reported via > zmq_poll() (either as ZMQ_POLLERR or a new ZMQ_POLLPEERSTATUS or > something like that), or if you want to get really fancy, report them > back to the app via a special inproc PUB/SUB socket. I like the > latter, but it's more like a high-level API while the rest of libzmq > is currently more like a low-level socket API. A higher-level library > could always build the latter on top of the former. > > By the way, my complaining is a form of flattery. I wouldn't bother > complaining about something I didn't really want to use. ZMQ is > pretty cool and has a lot of promise, it just has a little more > maturing to do. > _______________________________________________ > 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
