Re[3]: [log4perl-devel] modules logging into seperate logfiles

[Vince V. <vi...@ly...>]

Hello Mike,

MS> The big problem with having libraries add their share to the L4P configuration
MS> is that there's no easy way of preventing them from stepping on each
MS> other's feet.
In my situation all libs belong to one bigger SW and I did not even
think about the problem, that they might 'step on each others feet'.

But while thinking about reusable code I think it won't be easy to get
loggers which don't mess up with others unless there is so. who
controlls them.

Well... I ain't got Ideas, sorry.

Best regards,
 Vince                            mailto:vi...@ly...

-----

Monday, July 14, 2003, 10:35:21 PM, you wrote:

>> But I'd like my modules to log into different files absoluteley
>> indepently 'cause I'll have a lot of them working with each other
>> without having a "master" script that controlles them. There will be
>> more than one script that starts stuff and uses them. Therefore every
>> module shall be in charge of it's own logging...
>>
>> Is this against the fundamental idea of log4perl or is there a way to
>> accomplish this?

MS> Sorry for the long wait, here's a couple of thoughts on this:

MS> There's currently no way in Log::Log4perl to load more than one config file
MS> or to append configuration statements to a loaded configuration. This could
MS> be changed, however, if we find a proper way of dealing with the following
MS> implications:

MS> The big problem with having libraries add their share to the L4P configuration
MS> is that there's no easy way of preventing them from stepping on each
MS> other's feet. What if lib A defines an appender named "File" and lib B
MS> defines a different appender under the same name? What if the main application
MS> wants to take control over lib X's L4P configuration? How could lib X
MS> possibly know what kind of application it is going to run in and what the
MS> l4p configuration requirements are?

MS> Ideas?

MS> -- Mike

MS> Mike Schilli
MS> log...@pe...
MS> http://perlmeister.com
MS> http://log4perl.sourceforge.net


MS> -------------------------------------------------------
MS> This SF.Net email sponsored by: Parasoft
MS> Error proof Web apps, automate testing & more.
MS> Download & eval WebKing and get a free book.
MS> www.parasoft.com/bulletproofapps1
MS> _______________________________________________
MS> log4perl-devel mailing list
MS> log...@li...
MS> https://lists.sourceforge.net/lists/listinfo/log4perl-devel

MS> .