Serialization and deserialization

• US 8,131,860 B1
• Filed: 03/30/2006
• Issued: 03/06/2012
• Est. Priority Date: 03/30/2006
• Status: Active Grant

• Current Assignee: EMC Corporation (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Wong, Chee, Kasanagottu, Rajesh
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): SHIU, HO T
• Application Number:
  US11/393,199
• Time in Patent Office: 2,168 Days
• Field of Search: None
• US Class Current: 709/228
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Serialization is disclosed. It is detected if a component included in a graph of components associated with a user session on a first system has not changed since a prior serialization to a second system. A token is sent to the second system during a current serialization, instead of the component, indicating the component has not changed since the prior serialization. De-serialization is disclosed. a token is received at a first system from a second system, in a stream of serialized data from the second system, that indicates that a component on the second system has not changed since a prior serialization. A cached version of the component is retrieved. The cached copy is used to reconstruct on the second system a state of a user session with which the component is associated on the second system.

Claims

1. A method for serialization comprising:

detecting if a component included in a list of components associated with a user session on a first system has not changed since a prior serialization to a second system, wherein the list of components comprises a list of a plurality of components previously serialized and an identifier associated with each of the plurality of components;

indicating to a native serialization process to include a custom data in a serialization stream in place of a component that has not changed since the prior serialization;

wherein a flag is configured to indicate a component included in the list of components has been modified since the prior serialization;

wherein the flag is in a state indicating the component has been modified since the last serialization, sending to the second system during a current serialization, the changed component, and the custom data including a token indicating the component has not changed since the prior serialization and comprising at least the identifier associated with the component, wherein a serialization transfers state information of the user session from the first system to the second system enabling the second system to continue the user session in the event that the first system fails without the user being made aware of the changes;

clearing the flag that indicates the component has been modified once the component has been serialized; and

wherein in the event the list of components does not include any flags and/or tokens, the native serialization process would re-serialize any component regardless of whether the component has been modified since the prior serialization.

2. A method as in claim 1, wherein the token comprises a data value indicating the component has not changed.

3. A method as in claim 1, wherein the second system is configured to interpret the token as indicating the component has not changed and to use a cached copy of the component as received in the prior serialization to reconstruct the user session in connection with the current serialization.

4. A method as in claim 1, wherein the first system comprises a primary application server, the second system comprises a secondary application server, the user session comprises one or more components on the primary application server, and the prior serialization created a copy of the user session on a secondary application server.

5. A method as in claim 1, wherein detecting if a component has not changed since a prior serialization is based at least in part on checking a flag associated with the component.

6. A method as in claim 1, further comprising sending to the second system during the current serialization of a data associated with the user session.

7. A method as in claim 1, further comprising determining whether the component has been modified since the prior serialization.

8. A method as in claim 1, further comprising serializing the component in the event that the component has been modified since the prior serialization.

9. A method as in claim 8, wherein serializing the component comprises indicating that the component is to be included in a serialization stream.

10. A method as in claim 1, further comprising:

detecting that the component has changed since a prior serialization to a second system, wherein the component comprises a first subcomponent and a second subcomponent, wherein the first subcomponent has changed since the prior serialization and the second subcomponent has not changed since the prior serialization; and

sending to the second system during the current serialization a token indicating the second subcomponent has not changed since the prior serialization.

11. A system for serialization comprising:

a processor configured to;

detect if a component included in a list of components associated with a user session on a first system has not changed since a prior serialization to a second system, and wherein the list of components comprises a list of a plurality of components previously serialized and an identifier associated with each of the plurality of components;

indicate to a native serialization process to include a custom data included in a serialization stream in place of a component that has not changed since the prior serialization;

wherein a flag is configured to indicate a component included in the list of components has been modified since the prior serialization;

wherein the flag is in a state indicating the component has been modified since the last serialization, send to the second system during a current serialization, the changed component, and the custom data including a token indicating the component has not changed since the prior serialization and comprising at least the identifier associated with the component, wherein a serialization transfers state information of the user session from the first system to the second system enabling the second system to continue the user session in the event that the first system fails without the user being made aware of the changes;

clearing the flag that indicates the component has been modified once the component has been serialized;

wherein in the event the list of components does not include any flags and/or tokens, the native serialization process would re-serialize any component regardless of whether the component has been modified since the prior serialization; and

a memory coupled with the processor and configured to provide the processor with instructions.

12. A system as in claim 11, wherein the token comprises a data value indicating the component has not changed.

13. A system as in claim 11, wherein the second system is configured to interpret the token as indicating the component has not changed and to use a cached copy of the component as received in the prior serialization to reconstruct the user session in connection with the current serialization.

14. A system as in claim 11, wherein the first system comprises a primary application server, the second system comprises a secondary application server, the user session comprises one or more components on the primary application server, and the prior serialization created a copy of the user session on a secondary application server.

15. A system as in claim 11, wherein detecting if a component has not changed since a prior serialization is based at least in part on checking a flag associated with the component.

16. A system as in claim 11, wherein the processor is further configured to send to the second system during the current serialization of a data associated with the user session.

17. A system as in claim 11, wherein the processor is further configured to determine whether the component has been modified since the prior serialization.

18. A system as in claim 11, wherein the processor is further configured to serialize the component in the event that the component has been modified since the prior serialization.

19. A system as in claim 18, wherein serializing the component comprises indicating that the component is to be included in a serialization stream.

20. A system as in claim 11, wherein the processor is further configured to:

detect that the component has changed since a prior serialization to a second system, wherein the component comprises a first subcomponent and a second subcomponent, wherein the first subcomponent has changed since the prior serialization and the second subcomponent has not changed since the prior serialization; and

send to the second system during the current serialization a token indicating the second subcomponent has not changed since the prior serialization.

21. A computer program product for serialization, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:

detecting if a component included in a list of components associated with a user session on a first system has not changed since a prior serialization to a second system, wherein the list of components comprises a list of a plurality of components previously serialized and an identifier associated with each of the plurality of components;

indicating to a native serialization process to include a custom data in a serialization stream in place of a component that has not changed since the prior serialization;

wherein a flag is configured to indicate a component included in the list of components has been modified since the prior serialization;

wherein the flag is in a state indicating the component has been modified since the last serialization, sending to the second system during a current serialization, the changed component, and the custom data including a token indicating the component has not changed since the prior serialization and comprising at least the identifier associated with the component, wherein a serialization transfers state information of the user session from the first system to the second system enabling the second system to continue the user session in the event that the first system fails without the user being made aware of the changes;

clearing the flag that indicates the component has been modified once the component has been serialized; and

wherein in the event the list of components does not include any flags and/or tokens, the native serialization process would re-serialize any component regardless of whether the component has been modified since the prior serialization.