On Jan 7, 2008, at 10:16 PM, Adam Jacob wrote:
On 1/7/08, Jason Kohles <[EMAIL PROTECTED]> wrote:
It's also kind of a pain. I use log4perl with Catalyst, but without
the plugin, primarily for three reasons:
Patches are gladly accepted, especially if they make things better,
and don't break backwards compatibility.
I'm not saying the module is broken, just that some of it's goals
(being able to abort at any point during the request and have all the
logs for that request suppressed) were incompatible with some of my
goals (having the logs arrive in real-time). I was willing to make
the trade-off of not being able to suppress _all_ the logs for a given
aborted request, but it's not something that can be patched in a
backwards-compatible manner.
I started to put a patch together, but when I discovered that my goals
couldn't be met in a backwards compatible way I postponed it. When I
get some free time this week I'll try and finish that up and get it to
you.
--
Jason Kohles, RHCA RHCDS RHCE
[EMAIL PROTECTED] - http://www.jasonkohles.com/
"A witty saying proves nothing." -- Voltaire
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
