The current RemotingAppender does not deliver the events asynchronously. It will buffer the events but once the buffer is full it will send them synchronously.
The RemotingAppender in CVS will send the events asynchronously using a ThreadPool worker request. If you need this functionality now you can grab the latest version of the appender here: http://cvs.apache.org/viewcvs.cgi/logging-log4net/src/Appender/RemotingAppen der.cs?rev=1.3&view=auto Cheers, Nicko > -----Original Message----- > From: rohit s [mailto:[EMAIL PROTECTED] > Sent: 29 March 2004 15:46 > Subject: problem with RemotingAppender Calls > > > I am using Log4Net with RemotingAppender. I want a facility > of asynchronous message logging that means my client should > NOT wait till the message is getting logged by Remoting > Appender. To solve this purpose, I am thinking to use MSMQ. > But I was going thru config settings of Remoting Appender and > found one setting named "BufferSize" which says number of > events to buffer before giving it to the remote sink. > By looking at this setting, I was wondering if Remoting > Appender itself is implementing asynchronous message logging. > If this is so, then I would not be required to implement MSMQ stuff. > Please confirm me regarding this that whether Remoting > Appender implements asynchronous calling mechanism or not. >
