<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>It Makes the WWW Go Round, Part 1: IRequestChannel</title><link>http://blogs.msdn.com/drnick/archive/2006/03/15/551764.aspx</link><description>The final WCF message exchange pattern that I'm going to look at is the request-reply version of two-way communication. You may be familiar with the request-reply model as the native way to think about HTTP communication. Request-reply connections can</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>...Can Also Come Out (IOutputChannel)</title><link>http://blogs.msdn.com/drnick/archive/2006/03/15/551764.aspx#551987</link><pubDate>Wed, 15 Mar 2006 18:56:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:551987</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>Yesterday, we got a look at the reader side of the one-way communication pattern, which is implemented...</description></item><item><title>It Makes the WWW Go Round, Part 2: IReplyChannel</title><link>http://blogs.msdn.com/drnick/archive/2006/03/15/551764.aspx#555610</link><pubDate>Mon, 20 Mar 2006 19:12:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:555610</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>After a short break, let's continue looking at the request-reply message pattern.&amp;amp;amp;nbsp; In the previous...</description></item><item><title>It Makes the WWW Go Round, Part 3: IRequestContext</title><link>http://blogs.msdn.com/drnick/archive/2006/03/15/551764.aspx#556666</link><pubDate>Tue, 21 Mar 2006 19:03:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:556666</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>The final player in the drama between IRequestChannel and IReplyChannel is the link connecting requests...</description></item><item><title>Building a Custom File Transport, Part 1: Planning</title><link>http://blogs.msdn.com/drnick/archive/2006/03/15/551764.aspx#578340</link><pubDate>Tue, 18 Apr 2006 19:16:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578340</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>During the last few weeks I've been going over various parts of the channel model and giving some commentary...</description></item><item><title>HTTP Request and Response Messages</title><link>http://blogs.msdn.com/drnick/archive/2006/03/15/551764.aspx#623108</link><pubDate>Fri, 09 Jun 2006 03:23:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:623108</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>I've talked about the request-reply message exchange pattern that HTTP uses, but we've never looked at...</description></item></channel></rss>