On Fri, Feb 04, 2005 at 10:29:25AM -0500, Cees Hek wrote:
> Sorry for the late reply William...
No worries, Cees.
> That is the reason I switched away from Log::Log4perl.
Yeah, that seems like a major issue with the package. I suppose that the
group it's aimed at is okay with having central logging management.
> 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.
I'll try to remember to let you know once I get it implemented across
two applications.
> 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.
Good point. I suppose that in production, I shouldn't be sending that
many messages to the error log (or something is dreadfully wrong if I am
;).
> Thanks for that, I have fixed those...
Great. I look forward to working with your plugin.
William
--
Knowmad Services Inc.
http://www.knowmad.com
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
