<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Articles by Graham P. Harrison</title>
<link>http://ajax.sys-con.com/</link>
<description>Latest articles from Graham P. Harrison</description>
<copyright>Copyright 2008 AJAX &amp; RIA JOURNAL</copyright>
<lastBuildDate>Sat, 05 Jul 2008 06:34:00 GMT</lastBuildDate>
<generator>AJAX &amp; RIA JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Integrating AJAX with JMX: Opposite Ends of the Systems Management Stack</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/276359.htm</guid><link>http://ajax.sys-con.com/read/276359.htm</link>
<pubDate>Mon, 16 Oct 2006 08:15:00 GMT</pubDate>
<description>AJAX and JMX are at opposite ends of the Systems Management stack. However, the emerging ubiquity of the AJAX model for rich browser clients has obscured the benefits the model provides in the architectural space for enhancing support patterns within the problem resolution pipeline.</description>

</item><item>
<title>Integrating AJAX with the JMX Notification Framework</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/163239.htm</guid><link>http://ajax.sys-con.com/read/163239.htm</link>
<pubDate>Wed, 14 Dec 2005 06:30:00 GMT</pubDate>
<description>AJAX and JMX are at opposite ends of the Systems Management stack. However, the emerging ubiquity of the AJAX model for rich browser clients has obscured the benefits the model provides in the architectural space for enhancing support patterns within the problem resolution pipeline.</description>

</item><item>
<title>Enterprise Strategy with Java</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/35981.htm</guid><link>http://ajax.sys-con.com/read/35981.htm</link>
<pubDate>Fri, 01 May 1998 00:00:00 GMT</pubDate>
<description>Increasingly, technologists are asked by strategists to state the capability of Java within a distributed component architecture. The larger corporate platform is mixed and the owning, interacting businesses must implement a framework technical architecture in which present and future components can co-exist and change with minimum impact. Larger installations contain data and applications at corporate and departmental levels across a heterogenous computing environment. Technologists, thus, have to articulate some of the values and norms of the business strategist as the business and technology surfaces merge.</description>

</item><item>
<title>Browsing the JDBC API</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/35968.htm</guid><link>http://ajax.sys-con.com/read/35968.htm</link>
<pubDate>Wed, 01 Apr 1998 00:00:00 GMT</pubDate>
<description>It is not easy to query the contents of a database without proprietary front end tools or a database-aware IDE. A database-aware toolkit should be able to connect to and work with a variety of databases (local and remote, application and corporate) without a shift in how we view the contents of different databases.</description>

</item><item>
<title>Prototyping an Advanced Calendar Class</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/35884.htm</guid><link>http://ajax.sys-con.com/read/35884.htm</link>
<pubDate>Wed, 01 Oct 1997 00:00:00 GMT</pubDate>
<description>It is possible to create a very attractive look-and-feel prototype of a Calendar-based browser application in JavaScript, but to compete with tough-minded mainframe legacy systems such as MEMO requires a highly functional and scalable working prototype to justify the continued investment and potential encapsulation of a large mainframe system.</description>

</item><item>
<title>Prototyping an Advanced Calendar Class Using JavaScript</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/35868.htm</guid><link>http://ajax.sys-con.com/read/35868.htm</link>
<pubDate>Mon, 01 Sep 1997 00:00:00 GMT</pubDate>
<description>It is possible to create a very attractive look-and-feel prototype of a Calendar-based browser application in JavaScript, but to compete with tough-minded mainframe legacy systems such as MEMO requires a highly functional and scalable working prototype to justify the continued investment and potential encapsulation of a large mainframe system.</description>

</item></channel></rss>