<?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: From Contract to Channel</title>
	<atom:link href="http://kennyw.com/work/indigo/58/feed" rel="self" type="application/rss+xml" />
	<link>http://kennyw.com/work/indigo/58</link>
	<description>Kenny Wolf's Thoughts of the Moment</description>
	<lastBuildDate>Tue, 09 Mar 2010 15:40:51 +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; Adapting Channel Shapes</title>
		<link>http://kennyw.com/work/indigo/58/comment-page-1#comment-267</link>
		<dc:creator>kennyw.com &#187; Blog Archive &#187; Adapting Channel Shapes</dc:creator>
		<pubDate>Thu, 23 Feb 2006 19:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/58#comment-267</guid>
		<description>[...] As I implied in an earlier post, there&#8217;s a little more to the ServiceModel Channel Shapes then meets the eye. What I listed in the contract-&gt;shape mapping last week shows all the possibilities of what ServiceModel will request. However, it glosses over the process of how the channel requested is mapped to your service method. When you use ServiceModel, you get an extra layered channel at the top of your channel stack. The &#8220;Service Channel&#8221; has logic to normalize channel shapes into one-way and request reply patterns. [...]</description>
		<content:encoded><![CDATA[<p>[...] As I implied in an earlier post, there&#8217;s a little more to the ServiceModel Channel Shapes then meets the eye. What I listed in the contract-&gt;shape mapping last week shows all the possibilities of what ServiceModel will request. However, it glosses over the process of how the channel requested is mapped to your service method. When you use ServiceModel, you get an extra layered channel at the top of your channel stack. The &#8220;Service Channel&#8221; has logic to normalize channel shapes into one-way and request reply patterns. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buddhike's Weblog</title>
		<link>http://kennyw.com/work/indigo/58/comment-page-1#comment-56</link>
		<dc:creator>Buddhike's Weblog</dc:creator>
		<pubDate>Wed, 02 Nov 2005 05:00:53 +0000</pubDate>
		<guid isPermaLink="false">http://kennyw.com/indigo/58#comment-56</guid>
		<description>&lt;strong&gt;Kenny got the sixth sense ;-)&lt;/strong&gt;



Last night I was thinking about the way service model determines
the channel shape for the communication....</description>
		<content:encoded><![CDATA[<p><strong>Kenny got the sixth sense <img src='http://kennyw.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </strong></p>
<p>Last night I was thinking about the way service model determines<br />
the channel shape for the communication&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
