# US 8,280,916 B2 · Data locality in a serialized object stream

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,280,916 B2
- Document ID: US8280916B2
- Status: Granted
- Kind: B2
- Application number: 11/537,974
- Filed: 2006-10-02
- Published: 2008-04-03
- Granted: 2012-10-02
- Earliest claimed: 2006-10-02
- Assignees: Autodesk, Inc.
- Inventors: Ravinder P. Krishnaswamy
- Web page: https://patentgrep.com/patent/US8280916B2

## CPC

- G06F 9/4493: {Object persistence}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computer-implemented method and apparatus for providing data locality in a serialized object stream. Data is extracted from an object into the serialized object stream, thereby creating a simple data stream. Data of a specified type is then relocated from the extracted data to a contiguous section within the serialized object stream, thereby creating an enhanced data stream. The enhanced data stream is formatted in such a manner as to provide backward compatibility with the simple data stream.

## Claims

### Claim 1

A computer-implemented method for providing data locality in a serialized object stream, comprising:
(a) extracting, in a computer, data from an object into a serialized object stream, thereby creating a simple data stream comprised of an offset, which is followed by other data, which is followed by object references, wherein the offset, other data and object references are all located between an object data start and object data end, and the offset is a relative offset from the object data start that points to the object references; and
(b) relocating, in the computer, data of a specified type from the extracted data to a specified location in the serialized object stream, thereby creating an enhanced data stream comprised of the offset, which is followed by the other data, which is followed by the relocated data, which is followed by the object references, wherein the offset, other data, relocated data and object references are all located between the object data start and object data end, the offset is the relative offset from the object data start that points to the object references, and the enhanced data stream is formatted in such a manner as to provide backward compatibility with the simple data stream, so that a program that is only capable of processing the simple data stream can access the enhanced data stream as the simple data stream.

### Claim 2 (depends on 1)

The method of claim 1, wherein the extracting step comprises streaming the data out of the object.

### Claim 3 (depends on 1)

The method of claim 1, wherein the object is a native object.

### Claim 4 (depends on 1)

The method of claim 1, wherein the object is a custom object and the data is extracted by a custom object enabler.

### Claim 5 (depends on 1)

The method of claim 1, wherein the relocated data is relocated to a contiguous section within the serialized object stream.

### Claim 6 (depends on 1)

The method of claim 1, wherein the relocated data is prepended to the object references.

### Claim 7 (depends on 1)

The method of claim 1, wherein the relocated data includes an offset, offset flag and presence indicator, the offset is a relative offset from the object references that points to the relocated data, the offset flag indicates a type of offset, and the presence indicator indicates whether the relocated data is prepended to the object references.

### Claim 8 (depends on 1)

The method of claim 1, wherein the enhanced data stream is processed as an existing data stream, due to the relocated data's reverse offset layout, thereby providing the backward compatibility.

### Claim 9 (depends on 1)

The method of claim 1, wherein the relocated data includes optional type information.

### Claim 10

An apparatus for providing data locality in a serialized object stream, comprising:
a computer; and
logic, performed by the computer, for:
(a) extracting data from an object into a serialized object stream, thereby creating a simple data stream comprised of an offset, which is followed by other data, which is followed by object references, wherein the offset, other data and object references are all located between an object data start and object data end, and the offset is a relative offset from the object data start that points to the object references; and
(b) relocating data of a specified type from the extracted data to a specified location in the serialized object stream, thereby creating an enhanced data stream comprised of the offset, which is followed by the other data, which is followed by the relocated data, which is followed by the object references, wherein the offset, other data, relocated data and object references are all located between the object data start and object data end, the offset is the relative offset from the object data start that points to the object references, and the enhanced data stream is formatted in such a manner as to provide backward compatibility with the simple data stream, so that a program that is only capable of processing the simple data stream can access the enhanced data stream as the simple data stream.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the logic for extracting comprises logic for streaming the data out of the object.

### Claim 12 (depends on 10)

The apparatus of claim 10, wherein the object is a native object.

### Claim 13 (depends on 10)

The apparatus of claim 10, wherein the object is a custom object and the data is extracted by a custom object enabler.

### Claim 14 (depends on 10)

The apparatus of claim 10, wherein the relocated data is relocated to a contiguous section within the serialized object stream.

### Claim 15 (depends on 10)

The apparatus of claim 10, wherein the relocated data is prepended to the object references.

### Claim 16 (depends on 10)

The apparatus of claim 10, wherein the relocated data includes an offset, offset flag and presence indicator, the offset is a relative offset from the object references that points to the relocated data, the offset flag indicates a type of offset, and the presence indicator indicates whether the relocated data is prepended to the object references.

### Claim 17 (depends on 10)

The apparatus of claim 10, wherein the enhanced data stream is processed as an existing data stream, due to the relocated data's reverse offset layout, thereby providing the backward compatibility.

### Claim 18 (depends on 10)

The apparatus of claim 10, wherein the relocated data includes optional type information.

### Claim 19

An article of manufacture comprising a non-transitory program storage medium readable by a computer and embodying instructions executable by the computer to perform a method for providing data locality in a serialized object stream, comprising:
(a) extracting, in a computer, data from an object into a serialized object stream, thereby creating a simple data stream comprised of an offset, which is followed by other data, which is followed by object references, wherein the offset, other data and object references are all located between an object data start and object data end, and the offset is a relative offset from the object data start that points to the object references; and
(b) relocating, in the computer, data of a specified type from the extracted data to a specified location in the serialized object stream, thereby creating an enhanced data stream comprised of the offset, which is followed by the other data, which is followed by the relocated data, which is followed by the object references, wherein the offset, other data, relocated data and object references are all located between the object data start and object data end, the offset is the relative offset from the object data start that points to the object references, and the enhanced data stream is formatted in such a manner as to provide backward compatibility with the simple data stream, so that a program that is only capable of processing the simple data stream can access the enhanced data stream as the simple data stream.

### Claim 20 (depends on 19)

The article of claim 19, wherein the extracting step comprises streaming the data out of the object.

### Claim 21 (depends on 19)

The article of claim 19, wherein the object is a native object.

### Claim 22 (depends on 19)

The article of claim 19, wherein the object is a custom object and the data is extracted by a custom object enabler.

### Claim 23 (depends on 19)

The article of claim 19, wherein the relocated data is relocated to a contiguous section within the serialized object stream.

### Claim 24 (depends on 19)

The article of claim 19, wherein the relocated data is prepended to the object references.

### Claim 25 (depends on 19)

The article of claim 19, wherein the relocated data includes an offset, offset flag and presence indicator, the offset is a relative offset from the object references that points to the relocated data, the offset flag indicates a type of offset, and the presence indicator indicates whether the relocated data is prepended to the object references.

### Claim 26 (depends on 19)

The article of claim 19, wherein the enhanced data stream is processed as an existing data stream, due to the relocated data's reverse offset layout, thereby providing the backward compatibility.

### Claim 27 (depends on 19)

The article of claim 19, wherein the relocated data includes optional type information.
