Mike Schilli wrote:
Tom Metro wrote:
It came about because the $logger object doesn't actually convey the
full state, so when serialized and passed to a remote method, the
remote logging reverts to default logging settings.
Yeah, the way it's currently implemented, a logger is only
On Thu, 18 Nov 2010, Tom Metro wrote:
It came about because the $logger object doesn't actually convey the
full state, so when serialized and passed to a remote method, the
remote logging reverts to default logging settings.
Yeah, the way it's currently implemented, a logger is only
I like the API Log::Log4perl provides, but using Log::Log4perl v1.28
I've encountered issues with the internal implementation that have been
very time consuming to resolve.
Most relate to the way Log4perl seems to store state in global or class
variables rather than in object or instance
On Tue, 16 Nov 2010, Tom Metro wrote:
1. Ability to create a library module that can use Log4perl, such that
if the calling code makes no use of Log4perl, it logs independently
with locally specified defaults, but if the caller does use Log4perl,
it picks up the callers settings.
Hi Tom,
the
