From: Scott Woods (scott.suzuki_at_[hidden])
Date: 2008-02-18 05:30:38
----- Original Message -----
From: "Jurko Gospodnetiæ" <jurko.gospodnetic_at_[hidden]>
Sent: Monday, February 18, 2008 4:42 PM
Subject: [boost] Logging library review.
> * Filtering based on logged data. E.g. imagine logging airplane
> takeoffs and landings and wanting to log only landings for airplanes
> coming in from Frankfurt.
> * Filtering log messages so that they end up getting written to only
> some destinations. E.g. specifying at run-time that you want information
> about those same airplanes from Frankfurt logged to the output screen
> while all output, including this one, gets logged to the main network
> logging server.
Could you elaborate a little here? Are you implying that the configurability
of the logging library does not extend to the behaviours described above?
Or that some canned filters might be provided by the library to ease the
pain of implementing those behaviours?
Or are you after something more explicit, i.e. the formalization of the
logging data say, into columns, and the ability to test presented messages
by reference to those columns?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk