blob: aaec7e91ac7607abdc9a9ac11735838d0cb02bda [file] [log] [blame]
<html dir="LTR">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" />
<meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5" />
<title>RemotingAppender.SendBuffer Method</title>
<xml>
</xml>
<link rel="stylesheet" type="text/css" href="MSDN.css" />
</head>
<body id="bodyID" class="dtBODY">
<div id="nsbanner">
<div id="bannerrow1">
<table class="bannerparthead" cellspacing="0">
<tr id="hdr">
<td class="runninghead">Apache log4net� SDK Documentation - Microsoft .NET Framework 4.0</td>
<td class="product">
</td>
</tr>
</table>
</div>
<div id="TitleRow">
<h1 class="dtH1">RemotingAppender.SendBuffer�Method�</h1>
</div>
</div>
<div id="nstext">
<p> Send the contents of the buffer to the remote sink. </p>
<div class="syntax">
<span class="lang">[Visual�Basic]</span>
<br />Overrides�Protected�Sub�SendBuffer( _<br />���ByVal <i>events</i>�As�<a href="log4net.Core.LoggingEvent.html">LoggingEvent()</a>�_<br />)</div>
<div class="syntax">
<span class="lang">[C#]</span>
<br />protected�override�<a href="ms-help://MS.NETFrameworkSDKv1.1/cpref/html/frlrfSystemVoidClassTopic.htm">void</a>�SendBuffer(<br />���<a href="log4net.Core.LoggingEvent.html">LoggingEvent[]</a><i>events</i><br />);</div>
<h4 class="dtH4">Parameters</h4>
<dl>
<dt>
<i>events</i>
</dt>
<dd>The events to send.</dd>
</dl>
<h4 class="dtH4">Remarks</h4>
<p> The events are not sent immediately. They are scheduled to be sent using a pool thread. The effect is that the send occurs asynchronously. This is very important for a number of non obvious reasons. The remoting infrastructure will flow thread local variables (stored in the <a href="ms-help://MS.NETFrameworkSDKv1.1/cpref/html/frlrfSystemRuntimeRemotingMessagingCallContextClassTopic.htm">CallContext</a>), if they are marked as <a href="ms-help://MS.NETFrameworkSDKv1.1/cpref/html/frlrfSystemRuntimeRemotingMessagingILogicalThreadAffinativeClassTopic.htm">ILogicalThreadAffinative</a>, across the remoting boundary. If the server is not contactable then the remoting infrastructure will clear the <b>ILogicalThreadAffinative</b> objects from the <b>CallContext</b>. To prevent a logging failure from having side effects on the calling application the remoting call must be made from a separate thread to the one used by the application. A <a href="ms-help://MS.NETFrameworkSDKv1.1/cpref/html/frlrfSystemThreadingThreadPoolClassTopic.htm">ThreadPool</a> thread is used for this. If no <b>ThreadPool</b> thread is available then the events will block in the thread pool manager until a thread is available. </p>
<h4 class="dtH4">See Also</h4>
<p>
<a href="log4net.Appender.RemotingAppender.html">RemotingAppender Class</a> | <a href="log4net.Appender.html">log4net.Appender Namespace</a></p>
<object type="application/x-oleobject" classid="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e" viewastext="true" style="display: none;">
<param name="Keyword" value="SendBuffer method">
</param>
<param name="Keyword" value="SendBuffer method, RemotingAppender class">
</param>
<param name="Keyword" value="RemotingAppender.SendBuffer method">
</param>
</object>
<hr />
<div id="footer"><a href='http://logging.apache.org/log4net/'>Copyright 2004-2011 The Apache Software Foundation.</a><br></br>Apache log4net, Apache and log4net are trademarks of The Apache Software Foundation.</div>
</div>
</body>
</html>