[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4net-dev
Subject:    RE: spi vs core WAS RE: newbie wanna be developer
From:       Nicko Cadell <nicko () neoworks ! com>
Date:       2004-06-06 17:31:38
Message-ID: 487B2B5FD092D411977400D0B73EB0A23B75DF () titan ! neoworks ! co ! uk
[Download RAW message or body]

Rich, 

> Can you tell me when you plan on releasing new code?  

Not with any great certainty. I am still working through the FxCop issues
and improving the NDoc documentation. When that is done it should be in good
shape for another code release.


> Is there anything that needs help that I could lend my hands to?

The core of log4net always needs more tests, documentation and examples. 

There are a number of appenders that need writing or updating:

* A socket appender (similar to the UdpAppender but Tcp rather than Udp)
* A message queue appender
* An xml-rpc appender
* A new DbAppender that uses the same schema as the new log4j DBAppender
* Update the SMTPAppender to use a separate SMTP agent. The System.Web.Mail
package may not be available on all platforms.

Nicko


> 
> Thanks
> Rich 
> 
> -----Original Message-----
> From: Nicko Cadell [mailto:nicko@neoworks.com]
> Sent: Sunday, June 06, 2004 8:01 AM
> To: 'Log4NET Dev'
> Subject: RE: spi vs core WAS RE: newbie wanna be developer
> 
> Rich,
> 
> The log4net.spi namespace has been renamed log4net.Core in 
> the cvs head. I don't think that the log4net.spi namespace 
> has ever existed in the apache cvs repository.
> 
> One of the easiest ways to browse around the repository is to 
> use the viewcvs web interface:
> http://cvs.apache.org/viewcvs.cgi/logging-log4net/src/
> 
> To find out what happens during log4net startup I suggest 
> that you first enable log4net internal debug 
> http://logging.apache.org/log4net/release/manual/faq.html#inte
> rnalDebug
> This will give you more of an insight into which order things 
> are happening inside log4net.
> 
> Usefull places to trace through the startup are in the 
> log4net.Core.LoggerManager the GetLogger methods, and in the 
> log4net.Core.DefaultRepositorySelector GetRepository and 
> CreateRepository methods. But as always the debugger is your friend.
> 
> Nicko
> 
> 
> > -----Original Message-----
> > From: Denis, Rich [mailto:Rich.Denis@ps.net]
> > Sent: 06 June 2004 03:58
> > To: Log4NET Dev
> > Subject: spi vs core WAS RE: newbie wanna be developer
> > 
> > Hello all,
> > 
> >   I found the answer to my earlier question by using WinCVS 
> instead of 
> > Tort CVS.  I now would like to know the difference between the core 
> > and the spi namepsaces.  It appears that there are similar 
> classes in 
> > each of the name spaces.  When is one used over the other?  
> Also can 
> > someone let me know where would be a good place start to 
> try and trace 
> > what is happening when log4net is initially fired up?  I
> > 
> >  
> > 
> > Thanks
> > 
> >  
> > 
> > Rich
> > 
> >  
> > 
> > ________________________________
> > 
> > From: Denis, Rich
> > Sent: Saturday, June 05, 2004 9:26 PM
> > To: log4net-dev@logging.apache.org
> > Subject: newbie wanna be developer
> > 
> >  
> > 
> >  
> > 
> > Hello all,
> > 
> >  
> > 
> >   I am a long time log4net user wanting to actually get into 
> > developing log4net and possibly helping contribute to the 
> > community.  I am currently trying to get Tortoise CVS to 
> > connect to the repository correctly.  I have been able to use 
> > Cygwin's cvs tool to get the source but I would like to us 
> > Tortoise CVS.  I get a message saying 
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> > Empty password used - try 'cvs login' with a real password
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> > Can anyone help here?  Thanks.
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> > Rich
> > 
> > 
> 
[prev in list] [next in list] [prev in thread] [next in thread]