The mission statement is at http://logging.apache.org/site/mission-statement.html
The summary is: The Logging Services project is intended to provide cross-language logging services for purposes of application debugging and auditing. > -----Original Message----- > From: Matthew Griffore [mailto:[EMAIL PROTECTED] > Sent: 03 March 2004 18:35 > To: 'Log4NET User' > Subject: RE: [Log4net-users] SocketAppender > > What are some of the goals or directives of the Apache > Logging Services project? > > > -----Original Message----- > >From: Nicko Cadell <[EMAIL PROTECTED]>@DUKEPOWER > >Sent: March 3, 2004 1:09 PM > >To: 'Happe, Kevin'; 'Log4NET User' > >Cc: [EMAIL PROTECTED] > >Subject: RE: [Log4net-users] SocketAppender > > > >Kevin, > > > >The short answer is that I don't know! But this is exactly > the sort of > >thing that the http://logging.apache.org project was setup > to achieve. > > > >Currently log4net does not have a built-in SocketAppender, > the primary > >network appender is the RemotingAppender. I don't know if > log4cxx has a > >SocketAppender and if it does what it puts onto the wire. > > > >To get this to work you need to get log4net and log4cxx to > use the same > >transport, probably tcp/ip sockets. And you need to agree on > a wire format. > >If possible I would suggest an XML based format. It may not > be the most > >optimised wire protocol but it is the most robust for > interoperability. > > > >Log4net certainly supports recreating and re-logging events, however > >the only transport implemented currently is for .net remoting. It > >should not be too hard to implement a socket based transport > in C# for log4net. > > > >Nicko >
