# US 8,280,917 B1 · Batching content management operations to facilitate efficient database interactions

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

- Number: US 8,280,917 B1
- Document ID: US8280917B1
- Status: Granted
- Kind: B1
- Application number: 12/005,061
- Filed: 2007-12-21
- Granted: 2012-10-02
- Earliest claimed: 2007-12-21
- Assignees: EMC Corporation
- Inventors: Shu-Shang Sam Wei; Roger W. Kilday; Victor Spivak; Meir Amiel; David Buccola; Bryce Noland
- Web page: https://patentgrep.com/patent/US8280917B1

## CPC

- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Batching content management operations to facilitate efficient database interactions is disclosed. Two or more content management-related requests are received. The two or more content management-related requests are treated as a batch, including by formulating and sending to a database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records.

## Claims

### Claim 1

A method for managing stored content, comprising:
receiving two or more content management-related requests originally assigned to be processed together as part of a batch, wherein a batch of content management-related requests comprises requests that are sent to a database before a change to the database corresponding to the requests is committed;
storing the received content management-related requests in a queue;
after receiving the two or more content management-related requests, receiving an additional content management-related request originally assigned to be processed together with the two or more content management-related requests as part of the batch;
using a processor to determine whether the received additional content management-related request has a dependency upon at least one of the content management-related requests stored in the queue; and
in response to determining that the received additional content management-related request has a dependency upon at least one of the stored content management-related requests, processing only the two or more content management-related requests together as the batch, comprising:
excluding any later content management-related requests to be processed together with the two or more content management-related requests as the batch;
performing the two or more content management-related requests stored in the queue as the batch, including by formulating and sending to the database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records; and
delaying to perform the additional content management-related request after the two or more content management-related requests are performed.

### Claim 2 (depends on 1)

The method of claim 1, further comprising receiving from a requesting entity with which the two or more content management-related requests are associated an indication that the two or more content management-related requests are associated.

### Claim 3 (depends on 2)

The method of claim 2, wherein the indication comprises an explicit indication that the two or more content management-related requests comprise a batch.

### Claim 4 (depends on 1)

The method of claim 1, wherein processing only the two or more content management-related requests together as the batch is performed in the event it is determined to flush the stored content management-related requests even if an end of the batch has not been reached or indicated.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
using a processor to determine whether a query is received, wherein the query implicates an object that is affected by an as yet unperformed request in the queue; and
in response to receiving the query, processing only the two or more content management-related requests together as the batch.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
using a processor to determine whether an indication that a memory being used to store the queue is full or nearly full; and
in response to receiving the indication, processing only the two or more content management-related requests together as the batch.

### Claim 7

A content management system, comprising:
a communication interface configured to receive two or more content management-related requests originally assigned to be processed together as part of a batch, wherein a batch of content management-related requests comprises requests that are sent to a database before a change to the database corresponding to the requests is committed; and
a processor configured to:
store the received content management-related requests in a queue;
after receiving the two or more content management-related requests, receive an additional content management-related request originally assigned to be processed together with the two or more content management-related requests as part of the batch;
determine whether the received additional content management-related request has a dependency upon at least one of the content management-related requests stored in the queue; and
in response to determining that the received additional content management-related request has a dependency upon at least one of the stored content management-related requests, process only the two or more content management-related requests together as the batch, comprising:
exclude any later content management-related requests to be processed together with the two or more content management-related requests as the batch;
perform the two or more content management-related requests stored in the queue as the batch, including by formulating and sending to the database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records; and
delay to perform the additional content management-related request after the two or more content management-related requests are performed.

### Claim 8 (depends on 7)

The content management system of claim 7, wherein the processor is further configured to receive from a requesting entity with which the two or more content management-related requests are associated an indication that the two or more content management-related requests are associated.

### Claim 9 (depends on 8)

The content management system of claim 8, wherein the indication comprises an explicit indication that the two or more content management-related requests comprise a batch.

### Claim 10 (depends on 7)

The content management system of claim 7, wherein treating the two or more content management-related requests as a batch is performed in the event it is determined to flush the stored content management-related requests even if an end of the batch has not been reached or indicated.

### Claim 11 (depends on 7)

The content management system of claim 7, wherein the processor is further configured to:
determine whether a query is received, wherein the query implicates an object that is affected by an as yet unperformed request in the queue; and
in response to receiving the query, process only the two or more content management-related requests together as the batch.

### Claim 12 (depends on 7)

The content management system of claim 7, wherein the processor is further configured to:
determine whether an indication that a memory being used to store the queue is full or nearly full; and
in response to receiving the indication, process only the two or more content management-related requests together as the batch.

### Claim 13

A computer program product for managing stored content, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving two or more content management-related requests originally assigned to be processed together as part of a batch, wherein a batch of content management-related requests comprises requests that are sent to a database before a change to the database corresponding to the requests is committed;
storing the received content management-related requests in a queue;
after receiving the two or more content management-related requests, receiving an additional content management-related request originally assigned to be processed together with the two or more content management-related requests as part of the batch;
determining whether the received additional content management-related request has a dependency upon at least one of the content management-related requests stored in the queue; and
in response to determining that the received additional content management-related request has a dependency upon at least one of the stored content management-related requests, processing only the two or more content management-related requests together as the batch, comprising:
excluding any later content management-related requests to be processed together with the two or more content management-related requests as the batch;
performing the two or more content management-related requests stored in the queue as the batch, including by formulating and sending to the database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records; and
delay to perform the additional content management-related request after the two or more content management-related requests are performed.

### Claim 14 (depends on 13)

The computer program product recited in claim 13, further comprising computer instructions for receiving from a requesting entity with which the two or more content management-related requests are associated an indication that the two or more content management-related requests are associated.

### Claim 15 (depends on 14)

The computer program product recited in claim 14, wherein the indication comprises an explicit indication that the two or more content management-related requests comprise a batch.

### Claim 16 (depends on 13)

The computer program product of claim 13, wherein treating the two or more content management-related requests as a batch is performed in the event it is determined to flush the stored content management-related requests even if an end of the batch has not been reached or indicated.

### Claim 17 (depends on 13)

The computer program product of claim 13, further comprising computer instructions for:
determining whether a query is received, wherein the query implicates an object that is affected by an as yet unperformed request in the queue; and
in response to receiving the query, processing only the two or more content management-related requests together as the batch.

### Claim 18 (depends on 13)

The computer program product of claim 13, further comprising computer instructions for:
determining whether an indication that a memory being used to store the queue is full or nearly full; and
in response to receiving the indication, processing only the two or more content management-related requests together as the batch.
