Re: adding logging to Mason (need advice)

> I havn't used log4perl, but a logging system of some sort sounds like a 
> great idea.
> 
> Does the new plugin architecture expose enough functionality to write 
> this as a plugin
> or set of plugins?
> 
> Something like:
> Plugins::Log::Debug
> Plugins::Log::Fatal
> Plugins::Log::Inform
> 
> Doing it as a set of plugins which can be included/excluded should avoid 
> any performance hit,
> and would also provide a nice set of examples for hooking into various
> parts of the request for other potential plugin writers.

This would allow basic logging of request and components starting and 
finishing, but there are an order of magnitude more places that I want 
to log than there will be plugin hooks.

Although log4perl does let you assocate arbitrary "appenders" with 
categories of log messages, so if those appenders can run arbitrary 
code, then I guess in a way the logging system could be [ab]used as a 
plugin system.

Jon



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl