Re: [cgiapp] Re: ANNOUNCE: CGI::Application::Plugin::LogDispatch

[Cees Hek <suppressed>]

On Mon, 13 Dec 2004 17:31:26 +0000 (UTC), Mark Stosberg
<suppressed> wrote:
> On 2004-12-13, Cees Hek <suppressed> wrote:
> > On Mon, 13 Dec 2004 10:32:43 +0900, Thilo Planz <suppressed>
> > > I did not know about Log::Dispatch before, just Log4Perl, which seemed
> > > a little too complex for my needs.
> >
> > That was one of my main reasons for moving to Log::Dispatch.
>
> Could you elaborate a little on Log::Dispatch vs Log4Perl? I researched
> the options in the past and settled on Log4Perl.
> 
> However, I never got over the initial frustrations of getting to know
> Log4Perl stage, and went back to using no formal solution.  I still had
> the sense that Log4Perl had all the feature I wanted, but the effort to
> use it effectively was more than I wanted to invest, I think.

I settled on Log4perl for a while as well, but that was a long time
ago.  I'll list some of the reasons I decided to switch from what I
remember:

- Log::Log4perl creates a Singleton instance for the entire process
when you first use it.  This makes things very difficult in a mod_perl
environment where you have multiple projects with different logging
needs.  This is probably the mail reason I switched.
- So under mod_perl all your logging configuration needs to be in a
single config file.  Some might call that a benefit, but I have many
many apps running under mod_perl that really have nothing to do with
each other, and would like their logging to be managed separately.
- the configuration is too complex.  I spent hours trying to get it to
do anything more complex than just the examples in the perldocs
(probably my fault, but still an issue for me).
- the docs sometimes didn't give enough information (may be different
now), for example I could never figure out what a rootLogger was.  It
kept popping up in the examples, but was never explained.  Also
reading the code didn't give any hints as to what a rootLogger was...
- Log::Log4perl offers much more than I really need in a logging
module.  So why not use a simpler, and still very flexible module
instead.

All in all, I think that Log::Log4perl is a great module, it just
didn't fit my needs as well as Log::Dispatch does.  I like simplicity
over infinite configurability, and will usually gravitate to the
modules that do more of what I want, and less of what I don't need.

> Having a CGI::App plug-in is certainly one reason to choose
> Log::Dispatch. :)

Well, I'm sure someone could whip up a Log::Log4perl plugin pretty
quickly.  But I don't think it would solve the issues I have have with
it.  By the way, that was my main reason for calling it
CAP::LogDispatch, since I'm sure someone will write a Log4perl plugin.

Cheers,

-- 
Cees Hek

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed