System and method for managing an object cache

Patent metadata

Field	Value
Publication number	US-9792166-B2
Application number	US-201113289746-A
Country	US
Kind code	B2
Filing date	Nov 4, 2011
Priority date	Nov 4, 2011
Publication date	Oct 17, 2017
Grant date	Oct 17, 2017

Abstract

In order to optimize efficiency of serialization, a serialization cache is maintained at an object server. The serialization cache is maintained in conjunction with an object cache and stores serialized forms of objects cached within the object cache. When an object is to be sent from the server to the client, a serialization module determines if a serialized form of the object is stored in the serialization cache. If the object is already serialized within the serialization cache, the serialized form is retrieved and provided to the client. Otherwise, the object is serialized, the object is cached in the object cache and the serialized form of the object is cached in the serialization cache.

First claim

What is claimed is:

1. A method for serializing an object in a server that serves clients on plurality of serialization protocols comprising:
determining, by the server, an object to be serialized;
determining, by the server, a serialization protocol of the plurality of serialization protocols for the object to be serialized;
determining, by the server, if a serialization of the object of the determined serialization protocol is stored in a serialization cache; and
when a serialization of the object of the determined serialization protocol is stored in the serialization cache, retrieving, by the server, a serialized form of the object of the determined serialization protocol from the serialization cache;
wherein, when one or more immutables of the object are in-line with one or more primitives, the serialization cache stores two serializations of the object.

2. The method of claim 1 comprising providing the serialized form of the object retrieved from the serialization cache from the server to a client.

3. The method of claim 1 comprising when the object is not stored in the object cache:
serializing the object;
storing the object in the object cache; and
storing the serialized object in the serialization cache.

4. The method of claim 3 comprising associating the stored serialized object with the corresponding cached object.

5. The method of claim 1 comprising when the object is not stored in the object cache:
identifying a referenced object contained by the object to be serialized;
determining if the referenced object is stored in the object cache; and
when the referenced object is stored in the object cache, retrieving a serialized form of the referenced object from the serialization cache.

6. The method of claim 5 comprising:
serializing by a serialization module portions of the object to be serialized that cannot be retrieved from the serialization cache; and
aggregating one or more portion of the object to be serialized that are serialized by the serialization module with one or more portions of the object to be serialized retrieved from the serialization cache.

7. A caching server that serves clients on plurality of serialization protocols comprising:
at least one processor and at least one operatively associated memory, the at least one processor programmed to provide:
an object cache;
a serialization cache;
a request handler; and
a serialization module;
wherein the request handler is configured to determine a requirement to provide an object to a client;
wherein the serialization module is configured to:
determine if the object is cached in the object cache;
when the object is cached in the object cache:
determining a serialization protocol of the plurality of serialization protocols for the object to be serialized;
retrieve a corresponding serialization of the object of the determined serialization protocol from the serialization cache; and
provide the retrieved serialization of the object to the client;
wherein, when one or more immutables of the object are in-line with one or more primitives, the serialization cache stores two serializations of the object.

8. The server of claim 7 wherein the serialization module is configured to, when the object is not stored in the object cache:
serialize the object;
store the object in the object cache; and
store the serialization of the object in the serialization cache.

9. The server of claim 7 wherein the serialization cache is maintained for a plurality of serialization protocols.

10. The server of claim 7 comprising a plurality of serialization caches for a plurality of serialization protocols.

11. The server of claim 7 comprising a deserialization module, wherein the request handler is configured to receive a remote method invocation request comprising one or more serialized objects from a client and pass the one or more serialized objects to the deserialization module, and wherein the deserialization module is configured to:
reference the serialization cache to determine if one or more of the serialized objects received by the request handle are stored by the serialization cache;
for serialized objects that are stored by the serialization cache, retrieve an object corresponding to the serialized object from the object cache; and
for serialized objects that are not stored by the serialization cache:
deserialize the serialized object;
store the deserialized object in the object cache; and
store the serialized object in the serialization cache.

12. The server of claim 7 wherein the serialization module is configured to, when the object is not stored in the object cache:
identify a referenced object contained by the object to be serialized;
determine if the referenced object is stored in the object cache; and
when the referenced object is stored in the object cache, retrieving a serialized form of the referenced object from the serialization cache.

13. The server of claim 7 wherein the serialization module is configured to:
serialize portions of the object to be serialized that cannot be retrieved from the serialization cache; and
aggregate the portions serialized by the serialization module with portions of the object to be serialized retrieved from the serialization cache.

14. A method for serializing an object in a server that serves clients on plurality of serialization protocols comprising:
determining an object to be serialized;
determining a serialization protocol of the plurality of serialization protocols for the object to be serialized;
determining if a serialization of the object of the determined serialization protocol is stored in a serialization cache; and
when a serialization of the object of the determined serialization protocol is not stored in a serialization cache:
serializing the object for the determined serialization protocol;
storing the object in the object cache; and
storing the serialized object in the serialization cache;
wherein, when one or more immutables of the object are in-line with one or more primitives, the serialization cache stores two serializations of the object.

15. The method of claim 14 comprising associating the stored serialized object with the corresponding cached object.

16. The method of claim 14 comprising:
identifying a referenced object contained by the object to be serialized;
determining if the referenced object is stored in the object cache;
when the referenced object is stored in the object cache, retrieving a serialized form of the referenced object from the serialization cache.

17. The method of claim 16 comprising serializing portions of the object to be serialized that could not be retrieved from the serialization cache.

Assignees

• Ebdon Deren George
• Peterson Robert W
• Open Invention Network Llc

Inventors

• Ebdon Deren George
• Peterson Robert W

Classifications

• G06F9/548 Primary

  Object oriented; Remote method invocation [RMI] (non-remote method invocation G06F9/449) · CPC title