<?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>General things to take into consideration while doing socket programming.</title><link>http://blogs.msdn.com/malarch/archive/2006/06/26/647993.aspx</link><description>I had to recently write a client-server socket application and so I was mulling over all that needs to be considered when programming with sockets especially using TCP. I have summarized them below. 1. Partial Packets – Never assume that how much ever</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Recent System.Net Related Postings</title><link>http://blogs.msdn.com/malarch/archive/2006/06/26/647993.aspx#669307</link><pubDate>Tue, 18 Jul 2006 08:50:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:669307</guid><dc:creator>Windows Network Development</dc:creator><description>Recently, a number of current and former System.Net team members have posted about various managed code&amp;amp;amp;nbsp;network...</description></item><item><title>Recent System.Net Related Postings &amp;raquo; Wagalulu - Microsoft &amp;raquo;   &amp;raquo; Recent System.Net Related Postings</title><link>http://blogs.msdn.com/malarch/archive/2006/06/26/647993.aspx#669315</link><pubDate>Tue, 18 Jul 2006 08:52:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:669315</guid><dc:creator>Recent System.Net Related Postings » Wagalulu - Microsoft »   » Recent System.Net Related Postings</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoft.wagalulu.com/2006/07/18/recent-systemnet-related-postings/"&gt;http://microsoft.wagalulu.com/2006/07/18/recent-systemnet-related-postings/&lt;/a&gt;</description></item><item><title>Simple Message Framing Sample for TCP Socket</title><link>http://blogs.msdn.com/malarch/archive/2006/06/26/647993.aspx#1287264</link><pubDate>Thu, 14 Dec 2006 20:23:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1287264</guid><dc:creator>Jon Cole's WebLog</dc:creator><description>&lt;p&gt;A common misunderstanding for developers new to network programming over TCP sockets is how messages&lt;/p&gt;
</description></item><item><title>Simple Message Framing Sample for TCP Socket - Part 2 (Asynchronous)</title><link>http://blogs.msdn.com/malarch/archive/2006/06/26/647993.aspx#1287267</link><pubDate>Thu, 14 Dec 2006 20:24:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1287267</guid><dc:creator>Jon Cole's WebLog</dc:creator><description>&lt;p&gt;As a follow up to my last post ( &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/joncole/archive/2006/03/20/555721.aspx"&gt;http://blogs.msdn.com/joncole/archive/2006/03/20/555721.aspx&lt;/a&gt; ) I decided&lt;/p&gt;
</description></item><item><title>msdn socket programming</title><link>http://blogs.msdn.com/malarch/archive/2006/06/26/647993.aspx#8832652</link><pubDate>Tue, 05 Aug 2008 04:24:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8832652</guid><dc:creator>msdn socket programming</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://fabiola.videocardnews.info/msdnsocketprogramming.html"&gt;http://fabiola.videocardnews.info/msdnsocketprogramming.html&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>