On Mon, Nov 15, 2010 at 11:34 PM, Pieter Hintjens <p...@imatix.com> wrote: > OK, /me found a real keyboard and can explain this better. > > Here's my proposal for the topic header: > > * Number of repeated characters indicates severity from 1 to 3 (X = > information, XX = warning, XXX = error) > * Character indicates category of error: '?' indicates internal 0MQ > error, '*' indicates bad data, '#' indicates resource error, etc. > > Now I can subscribe to keys like '?' (any internal error), '***' (only > serious bad data errors and up), '##' (any resource errors apart from > informative). It is trivial to turn XXX into 3 if that's needed. > > This is just a sketch, we may want more severity levels eventually. > I'd probably not use version numbers in the API since it would be very > hard to manage multiple versions of the error subsystem at once. > > And we don't need multipart data, that is too complex. Just a topic > that specifies the severity and category, and then a textual message, > IMO. The simpler the better at this point.
One potential downside with this approach is that it could make it challenging to search for characters like '?'. You could get the same functionality through http-style number status codes, where informational messages are 1xx, client errors are 4xx, server errors are 5xx. You can subscribe to all of the error codes by subscribing to '4' and '5', or if you want just a specific message you subscribe to '401'. _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
