A nice idea, unfortunately though I'd still be blocked when I talked to the appender :(
-----Original Message----- From: Kevin Williams [mailto:[EMAIL PROTECTED] Sent: 02 June 2005 15:27 To: Log4NET User Subject: Re: ASP.NET Blocking Problem [EMAIL PROTECTED] wrote: > My concern with implementing buffering is that if my appdomain dies I > will lose the contents of the buffer. I've seen the app domain die in > testing and can't afford to lose the information in my live application. > I also have to guarantee that this data has reached the database > before I move on to actually do something (messaging isn't an option). Just a thought - I have no idea if it would work for you. Perhaps you could create a Remoting listener service (as in NT/200x/XP service) to do the database logging. You could communicate to that from the RemotingAppender. This could give you an asynchronous messaging buffer running in a separate AppDomain and, arguably, a more stable environment than ASP.NET. Cheers, Kevin -- ------------------------------------------------------------------------------ Halifax plc, Registered in England No. 2367076. Registered Office: Trinity Road, Halifax, West Yorkshire HX1 2RG. Authorised and regulated by the Financial Services Authority. Represents only the Halifax Financial Services Marketing Group for the purposes of advising on and selling life assurance, pensions and collective investment scheme business. ==============================================================================
