<?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>Protocol Channels</title><link>http://blogs.msdn.com/drnick/archive/2007/02/21/protocol-channels.aspx</link><description>There are only two kinds of channels in the world. Today we'll talk about protocol channels. Tomorrow we'll talk about transport channels. Transport channels move data to and from the network Protocol channels move data between the application and transport</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>When to Write a Channel</title><link>http://blogs.msdn.com/drnick/archive/2007/02/21/protocol-channels.aspx#1736457</link><pubDate>Wed, 21 Feb 2007 21:24:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1736457</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>&lt;p&gt;Today's article is about the tension between two simple points. Writing channels can generally be used&lt;/p&gt;
</description></item><item><title>re: Protocol Channels</title><link>http://blogs.msdn.com/drnick/archive/2007/02/21/protocol-channels.aspx#1766721</link><pubDate>Tue, 27 Feb 2007 05:29:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1766721</guid><dc:creator>Oran</dc:creator><description>&lt;p&gt;What about encoder channels? &amp;nbsp;Steve Swartz has repeatedly referred to 3 channel types: transport, encoder, and protocol.&lt;/p&gt;</description></item><item><title>re: Protocol Channels</title><link>http://blogs.msdn.com/drnick/archive/2007/02/21/protocol-channels.aspx#1766801</link><pubDate>Tue, 27 Feb 2007 05:59:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1766801</guid><dc:creator>Oran</dc:creator><description>&lt;p&gt;Whoops, I just got to your Transport Channels post mentioning encoders. &amp;nbsp;It's interesting you describe encoders as transport channel plugins rather than as channels in their own right.&lt;/p&gt;</description></item><item><title>re: Protocol Channels</title><link>http://blogs.msdn.com/drnick/archive/2007/02/21/protocol-channels.aspx#1766957</link><pubDate>Tue, 27 Feb 2007 06:57:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1766957</guid><dc:creator>Nicholas Allen</dc:creator><description>&lt;p&gt;Hi Oran,&lt;/p&gt;
&lt;p&gt;Message encoders are not channels. &amp;nbsp;A channel is something that implements one of the basic channel shapes that we'll look at in a few days. &amp;nbsp;MessageEncoder doesn't even implement IChannel. &amp;nbsp;The idea of a message encoder is really just a nicely reusable bit of implementation for our transport channels.&lt;/p&gt;
</description></item><item><title>Channel Writing Checklist (Required)</title><link>http://blogs.msdn.com/drnick/archive/2007/02/21/protocol-channels.aspx#1874425</link><pubDate>Tue, 13 Mar 2007 20:33:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1874425</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>&lt;p&gt;This pair of articles marks the checkpoint between the &amp;quot;big picture&amp;quot; introductory segments and the segments&lt;/p&gt;
</description></item></channel></rss>