Java object cache server for databases
DCFirst Claim
1. A method of providing a Java object from a cache server to a requesting system, the cache server being communicably coupled to a Java object database and one or more requesting systems, the method comprising:
- receiving a request from a requesting system, the request identifying a Java object;
responsive to said request, determining whether the identified Java object is stored in the cache server; and
if the identified Java object is stored in the cache server;
serializing the identified Java object into a byte stream to form a serialized Java object; and
sending the serialized Java object to the requesting system; and
if the identified Java object is not stored in the cache server;
instantiating the identified Java object;
serializing the instantiated Java object into a byte stream to form a serialized Java object; and
sending the serialized Java object to the requesting system.
2 Assignments
Litigations
0 Petitions
Accused Products
Abstract
A cache server is provided in a network for storing Java objects for retrieval by one or multiple application servers. Application server(s) are configured to request an object from the cache server, rather than requesting the Java object directly from a database, so as to reduce processing load on the database and free up database resources. Responsive to a request for a Java object from an application server, e.g., in an HTTP request, the cache server determines if the object is stored in memory and if so, serializes the requested object and sends the serialized object to the requesting server, e.g., in an HTTP response. The requesting server then deserializes the Java object. If the object is not stored in memory, the cache server instantiates the object (typically by requesting the object from the database), serializes the instantiated object and sends it to the requesting server. Cache coherency methods are also provided.
282 Citations
39 Claims
-
1. A method of providing a Java object from a cache server to a requesting system, the cache server being communicably coupled to a Java object database and one or more requesting systems, the method comprising:
-
receiving a request from a requesting system, the request identifying a Java object; responsive to said request, determining whether the identified Java object is stored in the cache server; and if the identified Java object is stored in the cache server; serializing the identified Java object into a byte stream to form a serialized Java object; and sending the serialized Java object to the requesting system; and if the identified Java object is not stored in the cache server; instantiating the identified Java object; serializing the instantiated Java object into a byte stream to form a serialized Java object; and sending the serialized Java object to the requesting system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 29, 30, 36, 37, 38, 39)
-
-
14. A Java object cache server communicably coupled to a Java object database and one or more requesting systems, the cache server comprising:
-
a processor; and a memory for storing Java objects, wherein the server is configured to; receive a request from a requesting system, said request identifying a Java object; determine whether the identified Java object is stored in the memory; and if the identified Java object is stored in memory; serialize the identified Java object into a byte stream to form a serialized Java object; and send the serialized Java object to the requesting system; and if the identified Java object is not stored in memory; instantiate the identified Java object; serialize the instantiated Java object into a byte stream to form a serialized Java object; and send the serialized Java object to the requesting system. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23, 31, 32, 33, 34, 35)
-
-
24. A method of rebuilding a Java object in a Java object cache server, comprising:
-
receiving an invalidation request, said invalidation request identifying a first Java object in the cache server; rebuilding the first Java object; maintaining an original copy of the first Java object in the cache server as the cache server is rebuilding the first Java object, such that the cache server is able to provide the original copy in response to a request for the first Java object as the first Java object is being rebuilt;
receiving a second invalidation request identifying the first Java object, said second invalidation request being received while the first Java object is being rebuilt;setting a flap in response to the second invalidation request; and after the first Java object has been rebuilt, rebuilding the first Java object responsive to the flag being set and according to the second invalidation request. - View Dependent Claims (25, 26, 27, 28)
-
Specification