<?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 Lloyd Hagemo</title>
 <link>http://websphere.sys-con.com/</link>
 <description>Latest articles from Lloyd Hagemo</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Wed, 20 Aug 2008 06:33:32 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>J2EE Application Performance Analysis</title>
 <link>http://websphere.sys-con.com/node/45688</link>
 <description>How well does your application perform? It is probably one of the toughest questions to answer accurately. It is not only a question of how many requests your application serves per second or per minute, but also how your application scales with respect to other performance metrics. It remains challenging to quantify application health quickly because there are a number of variables to consider.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/45688&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 04 Aug 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/45688</guid>
</item>
<item>
 <title>Hunting Java Memory Leaks</title>
 <link>http://websphere.sys-con.com/node/44716</link>
 <description>In a production environment, memory leaks can force organizations to add more memory and hardware resources. They can even cause an application to crash unexpectedly. In theory, Java memory leaks should not emerge as a development or production issue because the garbage collector is responsible for memory management.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/44716&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 05 May 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/44716</guid>
</item>
<item>
 <title>Creating a Framework - J2EE pattern frameworks provide template for flexible and modular architecture</title>
 <link>http://websphere.sys-con.com/node/43487</link>
 <description>Many patterns have been published for J2EE applications. By developing and connecting multiple patterns, developers can create a framework that improves the stability, performance, and scalability of their J2EE application architectures.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/43487&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 23 Jan 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/43487</guid>
</item>
<item>
 <title>One Access Point to Rule Them All - Front Controller pattern simplifies integration challenges</title>
 <link>http://websphere.sys-con.com/node/43449</link>
 <description>The concept of a central point of access to an application or set of applications is not new. For more than 30 years, companies have been writing, enhancing, and maintaining applications written to transactional systems such as CICS and IMS for IBM OS/390 mainframes.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/43449&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 24 Nov 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/43449</guid>
</item>
<item>
 <title>Dealing with Large Database Result Sets</title>
 <link>http://websphere.sys-con.com/node/43419</link>
 <description>When designing J2EE (Java 2 Platform, Enterprise Edition) applications, developers often find themselves challenged to create a display for  large database result sets. Improper treatment of the large result  set display can lead to poor response time and, ultimately, lost  productivity and sales.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/43419&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 24 Sep 2003 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/43419</guid>
</item>
<item>
 <title>Using Design Patterns to Streamline Future Development</title>
 <link>http://websphere.sys-con.com/node/43397</link>
 <description>Developers researching best practices for optimizing Java 2  Enterprise Edition (J2EE) environments can often find only general,  one-size-fits all suggestions for coding and tuning specific  application components. Although broad best practices can provide a  general direction for developers, the complexity associated with J2EE  programming requires a detailed set of guidelines to effectively  address specific development issues.&lt;p&gt;&lt;a href=&quot;http://websphere.sys-con.com/node/43397&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 15 Aug 2003 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://websphere.sys-con.com/node/43397</guid>
</item>
</channel>
</rss>
