<?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: On the Wire with channel.Open()/Close()</title>
	<atom:link href="http://kennyw.com/work/indigo/140/feed" rel="self" type="application/rss+xml" />
	<link>http://kennyw.com/work/indigo/140</link>
	<description>Kenny Wolf</description>
	<lastBuildDate>Tue, 27 Jul 2010 18:48:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: kennyw.com &#187; Blog Archive &#187; Dr. Nick on Message Framing</title>
		<link>http://kennyw.com/work/indigo/140/comment-page-1#comment-158611</link>
		<dc:creator>kennyw.com &#187; Blog Archive &#187; Dr. Nick on Message Framing</dc:creator>
		<pubDate>Tue, 03 Feb 2009 02:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/140#comment-158611</guid>
		<description>[...] #3-5 are the details behind the &quot;handshake&quot; I alluded to here. [...]</description>
		<content:encoded><![CDATA[<p>[...] #3-5 are the details behind the &quot;handshake&quot; I alluded to here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kennyw.com &#187; Blog Archive &#187; Client (TCP and Named Pipe) Connection Pooling</title>
		<link>http://kennyw.com/work/indigo/140/comment-page-1#comment-35739</link>
		<dc:creator>kennyw.com &#187; Blog Archive &#187; Client (TCP and Named Pipe) Connection Pooling</dc:creator>
		<pubDate>Wed, 14 Mar 2007 23:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/140#comment-35739</guid>
		<description>[...] That being said, the lifetime of the underlying socket is not necessarily 1-1 with the lifetime of the channel. Due to our connection pooling feature in WCF, a connection can be reused over the lifetime of multiple channels. We perform connection pooling for both buffered and streaming channels. Our connection pool is configurable through TcpConnectionPoolSettings/NamedPipeConnectionPoolSettings. These settings include a GroupName that we use for isolation, an upper bound on our cache size (MaxOutboundConnectionsPerEndpoint), and timeout values for reliability and NLB support [...]</description>
		<content:encoded><![CDATA[<p>[...] That being said, the lifetime of the underlying socket is not necessarily 1-1 with the lifetime of the channel. Due to our connection pooling feature in WCF, a connection can be reused over the lifetime of multiple channels. We perform connection pooling for both buffered and streaming channels. Our connection pool is configurable through TcpConnectionPoolSettings/NamedPipeConnectionPoolSettings. These settings include a GroupName that we use for isolation, an upper bound on our cache size (MaxOutboundConnectionsPerEndpoint), and timeout values for reliability and NLB support [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sajay Antony's Blog</title>
		<link>http://kennyw.com/work/indigo/140/comment-page-1#comment-19495</link>
		<dc:creator>Sajay Antony's Blog</dc:creator>
		<pubDate>Sat, 30 Dec 2006 04:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/140#comment-19495</guid>
		<description>&lt;strong&gt;Adding a Message Header without using a MessageContract...&lt;/strong&gt;

Using Message contracts is quite a straight forward way of creating and adding message headers.But then...</description>
		<content:encoded><![CDATA[<p><strong>Adding a Message Header without using a MessageContract&#8230;</strong></p>
<p>Using Message contracts is quite a straight forward way of creating and adding message headers.But then&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
