[cgiapp] CAP::LogDispatch questions

[William McKee <suppressed>]

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.

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.

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?

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 ).


William

-- 
Knowmad Services Inc.
http://www.knowmad.com

---------------------------------------------------------------------
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