Serialization and deserialization
First Claim
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.
8 Assignments
0 Petitions
Accused Products
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.
-
Citations
21 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
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. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
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.
-
Specification