<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: IReplyChannel and &#8220;null&#8221; replies</title>
	<atom:link href="http://kennyw.com/work/indigo/119/feed" rel="self" type="application/rss+xml" />
	<link>http://kennyw.com/work/indigo/119</link>
	<description>Kenny Wolf's Thoughts of the Moment</description>
	<lastBuildDate>Tue, 16 Mar 2010 09:01:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: kennyw.com &#187; Blog Archive &#187; On the Wire with channel.Open()/Close()</title>
		<link>http://kennyw.com/work/indigo/119/comment-page-1#comment-15864</link>
		<dc:creator>kennyw.com &#187; Blog Archive &#187; On the Wire with channel.Open()/Close()</dc:creator>
		<pubDate>Fri, 15 Dec 2006 03:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/119#comment-15864</guid>
		<description>[...] Abort()/Close() &#8212; If the associated HTTP Channel Listener has been disposed, then channel.Abort will in turn call HttpRequestContext.Abort() on any RequestContexts that have not been replied to. This will cause http.sys to abort the underlying TCP socket. If the HTTP Channel Listener has not been disposed then channel.Abort() simply transfers ownership of these outstanding request contexts back to the channel listener. Close() actually performs in the same fashion, since calling requestContext.Close() in this case would have the unexpected side-effect of sending a 202 Accepted response. [...]</description>
		<content:encoded><![CDATA[<p>[...] Abort()/Close() &#8212; If the associated HTTP Channel Listener has been disposed, then channel.Abort will in turn call HttpRequestContext.Abort() on any RequestContexts that have not been replied to. This will cause http.sys to abort the underlying TCP socket. If the HTTP Channel Listener has not been disposed then channel.Abort() simply transfers ownership of these outstanding request contexts back to the channel listener. Close() actually performs in the same fashion, since calling requestContext.Close() in this case would have the unexpected side-effect of sending a 202 Accepted response. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kennyw.com &#187; Blog Archive &#187; The effect of IsOneWay on Operations</title>
		<link>http://kennyw.com/work/indigo/119/comment-page-1#comment-2734</link>
		<dc:creator>kennyw.com &#187; Blog Archive &#187; The effect of IsOneWay on Operations</dc:creator>
		<pubDate>Thu, 06 Jul 2006 20:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/119#comment-2734</guid>
		<description>[...] The service will release the connection (or complete the HTTP request/response by replying with null, etc) before dispatching to user code. If the operation is not marked with IsOneWay then our Dispatcher won&#8217;t reply until the Operation has completed [...]</description>
		<content:encoded><![CDATA[<p>[...] The service will release the connection (or complete the HTTP request/response by replying with null, etc) before dispatching to user code. If the operation is not marked with IsOneWay then our Dispatcher won&#8217;t reply until the Operation has completed [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
