<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://dotnet.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Alexander Gladshtein</title>
 <link>http://dotnet.sys-con.com/</link>
 <description>Latest articles from Alexander Gladshtein</description>
 <language>en</language>
 <copyright>Copyright 2008 </copyright>
 <generator></generator>
 <lastBuildDate>Fri, 05 Dec 2008 04:47:28 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Exploring FTP in .NET 2.0</title>
 <link>http://dotnet.sys-con.com/node/294674</link>
 <description>Fall the network protocols missing from .NET 1.0 and 1.1, the most notable is the File Transfer Protocol (FTP). Manually implementing the protocol for software developers was an unreasonable expectation, especially considering the complexity of the protocol in comparison to such protocols as HTTP or TELNET. This led to a thriving third-party component industry that has been perfecting FTP implementations since VB3 (and has been an ideal example of the argument for buying versus building when FTP functionality was required, especially with a price point of around $250). With the coming of .NET 2.0, Microsoft has introduced a native FTP communications implementation, but with some very curious design decisions that may complicate programming sufficiently so as to make abandoning commercial FTP components ill-advisable for many users.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/294674&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 06 Nov 2006 12:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/294674</guid>
</item>
<item>
 <title>How To Implement Secure TCP Communications in Microsoft .NET 2.0</title>
 <link>http://dotnet.sys-con.com/node/113335</link>
 <description>The release of the .NET Framework 2.0 promises to be the first major upgrade to Windows and Web development tools since the initial release of .NET in 2001. In the realm of general networking, some of the major improvements to the Framework include FTP, Ping, packet tracing, and revised SMTP/MIME classes that are not dependent on the Windows SMTP service.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/113335&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 29 Jul 2005 00:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/113335</guid>
</item>
<item>
 <title>Building High-Performance and Scalable .NET Internet Applications</title>
 <link>http://dotnet.sys-con.com/node/38911</link>
 <description>There are significant benefits to using third-party components, and many programmers have come to depend on components to handle common tasks that would require either too much time or specialization for them to implement themselves. However, many programmers fail to realize that there are component options available for almost every need.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/38911&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 07 Jul 2003 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/38911</guid>
</item>
</channel>
</rss>
