<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Prior Art submitted for System and method for retaining information in a data management system</title>
    <link>http://peertopatent.org/patent/33/prior_art/list</link>
    <description>A system for retaining information in a data management system in which a memory manger is associated with a server, an interface is provided for controlling access to the memory manager, and one or more application components are adapted for implementing the interface. A method for retaining information in a data management system in which information is stored and retrieved from an external database into a memory associated with a server and access to the memory is enabled through an interface implemented by one or more application components. A machine-readable storage medium and machine readable code for implementing the same.</description>
    <language>en-us</language>
    <item>
      <title>WebSphere Application Server - Express V6 Developers Guide and Development Examples</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: WebSphere Application Server - Express V6 Developers Guide and Development Examples&lt;br/&gt;ISBN: 0738493678&lt;br/&gt;Description: A more recent product that implements the Java servelet standard that is described in other prior art. This product can store session information in memory or in a database.</description>
      <pubDate>Wed, 05 Sep 2007 21:08:47 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/74/detail</guid>
    </item>
    <item>
      <title>WebSphere Application Servers: Standard and Advanced Editions</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: WebSphere Application Servers: Standard and Advanced Editions&lt;br/&gt;ISBN: 0738413763&lt;br/&gt;Description: This describes IBM's WebSphere Application Server products in 1999. These products implemented the Java servelet standard, which is described in some of the other prior art cited here.</description>
      <pubDate>Wed, 05 Sep 2007 20:43:11 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/73/detail</guid>
    </item>
    <item>
      <title>Java Servlet Programming, 2nd Edition</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: Java Servlet Programming, 2nd Edition&lt;br/&gt;ISBN: 978-0596000400&lt;br/&gt;Description: Describes associating information on servers with browser sessions. See Chapter 7, &amp;quot;Session Tracking&amp;quot;, in particular. This may be easier to find than the first edition.</description>
      <pubDate>Wed, 05 Sep 2007 20:08:39 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/72/detail</guid>
    </item>
    <item>
      <title>Java Servlet Programming</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: Java Servlet Programming&lt;br/&gt;ISBN: 1-56592-391-X&lt;br/&gt;Description: Describes associating information on servers with browser sessions. See Chapter 7, &amp;quot;Session Tracking&amp;quot;, in particular.</description>
      <pubDate>Wed, 05 Sep 2007 15:51:47 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/71/detail</guid>
    </item>
    <item>
      <title>Encapsulating Session State Management in ColdFusion</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: Encapsulating Session State Management&lt;br/&gt;Description: ColdFusion developers rely on session state management and the SESSION scope extensively. But as applications grow in complexity, so do the number of SESSION variables, and the risk of overwriting or misusing them. It need not be that way; with a little work (and ColdFusion Components), SESSION use can be clean, simple, and highly organized.</description>
      <pubDate>Sat, 25 Aug 2007 22:52:27 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/64/detail</guid>
    </item>
    <item>
      <title>IBM DB2, Oracle, Ingress, Postgress, dBase, Filemaker, and every other DBMS</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: Oracle 7&lt;br/&gt;ISBN: &lt;br/&gt;Description: All data base management systems match claim 10.  Additionally, the claim is obvious, and not likely to have patent prior art.</description>
      <pubDate>Fri, 24 Aug 2007 20:39:10 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/62/detail</guid>
    </item>
    <item>
      <title>ASP.NET Session State</title>
      <category>System and method for retaining information in a data management system</category>
      <description>Title: ASP.NET Session State&lt;br/&gt;Description: Describes the various solutions available for Microsoft ASP.NET to persist session state so that it can be shared between web servers and thus survive server failure.</description>
      <pubDate>Fri, 24 Aug 2007 05:58:20 -0700</pubDate>
      <guid>http://peertopatent.org/prior_art/60/detail</guid>
    </item>
  </channel>
</rss>
