[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cgiapp] CAP::LogDispatch questions


Sorry for the late reply William...

On Fri, 28 Jan 2005 10:47:00 -0500, William McKee <suppressed> wrote:
> Thanks to Cees' plugin, I'm starting to look at converting from using
> Log::Log4perl to Log::Dispatch to handle logging in my applications. The
> primary reason for the switch is that Log::Log4perl is a singleton which
> must be configured globally for all applications. This improves
> performance in a persistent environment but is a headache if you are
> running multiple applications under a single mod_perl server.

That is the reason I switched away from Log::Log4perl.

> Cees has recently added Singleton support which sounds like it should
> allow individual configurations for different applications running under
> a single mod_perl server by using custom namespaces. I'm wondering if
> anyone is successfully using this technique with more than 1
> application.

I am not using mod_perl so I can't answer this one.   But the way I
implemented the singleton support will allow what you are looking for.
 I'd apreciate any feedback if you do test this successfully under
mod_perl with multiple applications.

> Also, while reading about the various Log::Dispatch modules available
> for logging, I came across Log::Dispath::File::Locked. I'm thinking that
> if running in a persistent environment (even if you're not), it's
> probably better to use file locking than the L::D::File module as shown
> in the examples for CAP::LogDispatch. Comments?

It is definately safer at the expense of a bit of performance.  I
guess you have to decide how critical the log info is.  I use the
::File logger more in debugging the app, not so much when it goes
live.  In production I usually only log errors to file and emergency
messages are mailed out.

> Finally, there's a typo in the POD examples under METHODS->log:
> 
>   # retrieve the log object
>   my $log = $self->log;
>   $log->warning("something's not right!";
>   $log->emergency("It's all gone pear shaped!";
> 
> Those last two lines are missing the ending ).

Thanks for that, I have fixed those...

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


Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.