Kevin, I meant bridging in the large sense: having Log::Log4perl call log4j appenders and also vice versa (why not?).
One relatively "low tech" solution is to have Log::Log4perl client to talk to a log4j server by sending serialized logging events. The next version of log4j is very likely to use the java.io.Externalizable interface which just might be simple enough to be reproduced by a perl client. The disadvantage of this solution is that it requires an additional process (the log4j server process). The advantage is that it is "low tech" using just TCP to bridge between perl and java logging. The same technique can also apply to bridging other languages. As you mentioned in your mail, another approach consists of embedding Java within Perl or directly calling java from perl. My unfounded suspicion is that this technique will be slow and too complex although I might be completely off base here. At 10:25 11.07.2002 -0700, Kevin Goess wrote: >Ceki, > >You mean have a perl call to the logger handled by the java appender? >Funny, I didn't even think of that. That would be interesting, I'm >going to add it to the feature list on sourceforge. These would all be >possible implementations: >Inline::Java - http://search.cpan.org/search?dist=Inline-Java >Java - http://search.cpan.org/search?dist=Java >Jvm - http://search.cpan.org/search?dist=Jvm > >Ceki Gülcü wrote: > > > > Mike, > > > > This is wonderful news. I wish a tool like Log::Log4perl existed at > > the time when I was doing serious Perl development. I'll update the > > downloads page asap. > > > > Do you think we could bridge between log4j appenders and Log::Log4perl > > appenders? Is that a venue that you would like to pursue? > > -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
