Systems and methods for fragment-based serialization
First Claim
1. A method for storing or transmitting a data object made of one or more data members, comprising:
- dividing a plurality of sequentially located bytes into at least one header section and at least one payload section; and
representing at least one data member in the payload section, wherein said at least one data member is associated with a data type; and
representing the data type in the header section; and
placing the at least one data member in the payload section in a record format, wherein the record format defines a predictable location for said at least one data member in relation to any other members in the payload section.
1 Assignment
0 Petitions
Accused Products
Abstract
A method and system for fragment-based serialization places one or more object members in fragments. Fragments may comprise a header and a payload. A header can provide useful information about the fragment, such as an indication of fragment type and an indication of fragment length. A payload may comprise one or more members of an object. Primitive members may be stored in a Binary Fragment with a record format payload. LOB and FS members may be stored in fragments that have a Value Type field for setting forth additional properties of the fragment. Collections may be stored in a series of fragments, a first fragment to indicate a start of a collection, one or more second fragments to serialize collection elements, and a Terminator Fragment to indicate the end of a collection. Fragment-serialized objects minimize storage overhead while providing fast instantiation and low-cost location and updating.
-
Citations
20 Claims
-
1. A method for storing or transmitting a data object made of one or more data members, comprising:
-
dividing a plurality of sequentially located bytes into at least one header section and at least one payload section; and
representing at least one data member in the payload section, wherein said at least one data member is associated with a data type; and
representing the data type in the header section; and
placing the at least one data member in the payload section in a record format, wherein the record format defines a predictable location for said at least one data member in relation to any other members in the payload section. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A computer readable medium bearing instructions for storing or transmitting a data object made of one or more data members, comprising:
-
instructions for dividing a plurality of sequentially located bytes into at least one header section and at least one payload section; and
instructions for representing at least one data member in the payload section, wherein said at least one data member is associated with a data type; and
instructions for representing the data type in the header section; and
instructions for placing the at least one data member in the payload section in a record format, wherein the record format defines a predictable location for said at least one data member in relation to any other members in the payload section. - View Dependent Claims (12, 13, 14, 15, 16)
-
-
17. A method for uniquely identifying a data object made of one or more data members, said method comprising:
-
determining a unique identifier for a non-primitive member in the object;
determining a subtype depth value for the object;
determining a locator identifier for a locator associated with the object;
using one or more of said unique identifier, said subtype depth, and said locator identifier to identify the data object. - View Dependent Claims (18, 19, 20)
-
Specification