Re: Running under mod_perl (was Re: [log4perl-devel] Can't call method "PRINT" on an undefined value)

[William M. <wi...@kn...>]

On Tue, Jan 13, 2004 at 12:53:38AM -0800, Mike Schilli wrote:
> I agree, using the startup handler to call init exactly once is 
> definitely the way to go for now. Hmm ... just had an idea: How about if 
> Log::Log4perl featured an init_once() method, like Apache::DBI, which 
> connects (inits) only if it doesn't have a valid connection 
> (configuration) yet? Or maybe we do Apache::Log::Log4perl :) ?

If you want to take on the task of creating a caching mechanism inside
of log4perl, I'd certainly take advantage of it. I wonder though if
that's the right place for it. Does log4j do this kind of caching? Will
anyone else need this support (I'm guessing so since you seemed to have
been considering it)?

I like the idea of a caching module like Apache::DBI that transparently
provides caching for log4perl objects. I'd be glad to do any testing for
you.

William

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