<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://websphere.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Paul Ilechko</title>
 <link>http://websphere.sys-con.com/</link>
 <description>Latest articles from Paul Ilechko</description>
 <language>en</language>
 <copyright>Copyright 2008 </copyright>
 <generator></generator>
 <lastBuildDate>Sun, 23 Nov 2008 10:28:24 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Breaking Down a Complex App Development Area</title>
 <link>http://websphere.sys-con.com/node/222906</link>
 <description>Database locking strategies is one of the most complex areas of application development -- and one of the most critical for reliable application performance and behavior. The basic issues, common strategies, and general recommendations on when and how to use different locking strategies are outlined in this article.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/222906&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 22 May 2006 11:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/222906</guid>
</item>
</channel>
</rss>
