On Thu, Feb 17, 2011 at 6:33 PM, Robert G. Jakabosky <[email protected]> wrote:
> What about allowing the log messages to be multi-part, with the identity (or > other optional log info) sent unformatted as the second part. This could also > decrease the overhead of sending log messages. > > Also if the first part of the log message was just the error identifier, then > a log formatting function could be provided to format the log message for > printing. Indeed... we will need a standard log message format, and this can go quite far. I'll godwin the thread by suggesting we use XML :-) > This logging feature could be used for detecting connect/disconnect events, > something that I and a few other people I talked to have wanted. > > Another way to get event notices from a socket would be to add a socket option > to set an address that events should be published to. > > connect/disconnect events could be used by publishers to know when they should > start/stop sending data or by load-balancers devices to detect the failure of > backend workers. Connection is not really the same as presence, which makes this tricky. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
