<?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>Tired of creating sockets for each protocol</title><link>http://blogs.msdn.com/malarch/archive/2005/11/18/494769.aspx</link><description>Tired of creating sockets for each protocol, to make your application listen on all addresses for a given port ? . There is no more pain. Here is a cool new feature supported in Vista and Windows Server Longhorn. By just setting a socketoption, you will</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Sample Asynchronous SslStream Client/Server Implementation</title><link>http://blogs.msdn.com/malarch/archive/2005/11/18/494769.aspx#3275661</link><pubDate>Thu, 14 Jun 2007 00:59:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3275661</guid><dc:creator>Jon Cole's WebLog</dc:creator><description>&lt;p&gt;I was recently asked about sample code for the System.Net.Security.SslStream using the asynchronous APIs.&lt;/p&gt;
</description></item></channel></rss>