# US 2015/0106426 A1 · Temporary content versioning on a client in a rest-based system

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

- Number: US 2015/0106426 A1
- Document ID: US20150106426A1
- Status: Published application
- Kind: A1
- Application number: 14/051,732
- Filed: 2013-10-11
- Published: 2015-04-16
- Earliest claimed: 2013-10-11
- Assignees: Adobe Systems Incorporated
- Applicants: Adobe Systems Incorporated
- Inventors: Damien Antipa
- Web page: https://patentgrep.com/patent/US20150106426A1

## CPC

- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques are disclosed for maintaining different versions of a web resource. A client-side application observes and tracks all asynchronous requests for web resources sent from the client to a server. Every time a user attempts to modify a resource on the server, the application stops or otherwise pauses the execution of the request and retrieves a representation of the resource from the server in an original state. The representation is stored locally on the client in a local storage, such as browser persistent storage, and may be stored with a timestamp and the corresponding resource URL. Subsequently, the request to modify the resource is executed. In this manner, a representation of the resource is retained in an original state prior to modification. The locally-stored representation can be used to restore the resource back to the original state in response to a so-called undo request by the user.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving, via a web browser, a first request to change a web resource in a stateless representational state transfer (REST)-compliant software architecture;
in response to receiving the first request, retrieving a representation of the web resource in an original state;
storing the representation of the web resource in the original state in a storage local to the web browser;
changing the web resource to a modified state according to the first request;
receiving a second request to restore the web resource to the original state; and
in response to receiving the second request, restoring the web resource to the original state based on the stored representation of the web resource in the original state.

### Claim 2 (depends on 1)

The method of claim 1, further comprising storing a representation of the web resource in the modified state in the storage.

### Claim 3 (depends on 2)

The method of claim 2, further comprising receiving a third request to restore the web resource to the modified state.

### Claim 4 (depends on 3)

The method of claim 3, further comprising, in response to receiving the third request, restoring the web resource to the modified state based on the stored representation of the web resource in the modified state.

### Claim 5 (depends on 1)

The method of claim 1, wherein retrieving the representation of the web resource in the original state includes receiving the representation in a JavaScript Object Notation (JSON) format.

### Claim 6 (depends on 1)

The method of claim 1, wherein the local storage includes a browser-persistent storage.

### Claim 7 (depends on 1)

The method of claim 1, wherein retrieving the representation of the web resource in the original state includes executing a GET request.

### Claim 8 (depends on 1)

The method of claim 1, wherein changing the web resource to the modified state includes executing a POST or PUT request.

### Claim 9 (depends on 1)

The method of claim 1, wherein the web resource is housed in a Content Repository Application Programming Interface for Java (JCR).

### Claim 10

A system comprising:
a storage local to a web browser; and
a processor operatively coupled to the storage and configured to carry out a process comprising:
receiving, via the web browser, a first request to change a web resource in a stateless representational state transfer (REST)-compliant software architecture;
in response to receiving the first request, retrieving a representation of the web resource in an original state;
storing the representation of the web resource in the original state in the storage;
changing the web resource to a modified state according to the first request;
receiving a second request to restore the web resource to the original state; and
in response to receiving the second request, restoring the web resource to the original state based on the stored representation of the web resource in the original state.

### Claim 11 (depends on 10)

The system of claim 10, wherein the process further comprises storing a representation of the web resource in the modified state in the storage.

### Claim 12 (depends on 11)

The system of claim 11, wherein the process further comprises receiving a third request to restore the web resource to the modified state.

### Claim 13 (depends on 12)

The system of claim 12, wherein the process further comprises, in response to receiving the third request, restoring the web resource to the modified state based on the stored representation of the web resource in the modified state.

### Claim 14 (depends on 10)

The system of claim 10, wherein retrieving the representation of the web resource in the original state includes receiving the representation in a JavaScript Object Notation (JSON) format.

### Claim 15 (depends on 10)

The system of claim 10, wherein retrieving the representation of the web resource in the original state includes executing a GET request.

### Claim 16 (depends on 10)

The system of claim 10, wherein changing the web resource to the modified state includes executing a POST or PUT request.

### Claim 17 (depends on 10)

The system of claim 10, wherein the web resource is housed in a Content Repository Application Programming Interface for Java (JCR).

### Claim 18

A non-transient computer-readable medium having instructions encoded thereon that when executed by a processor cause the processor to carry out a process comprising:
receiving, via a web browser, a first request to change a web resource in a stateless representational state transfer (REST)-compliant software architecture;
in response to receiving the first request, retrieving a representation of the web resource in an original state;
storing the representation of the web resource in the original state in a storage local to the web browser;
changing the web resource to a modified state according to the first request;
receiving a second request to restore the web resource to the original state; and
in response to receiving the second request, restoring the web resource to the original state based on the stored representation of the web resource in the original state.

### Claim 19 (depends on 18)

The computer-readable medium of claim 18, wherein retrieving the representation of the web resource in the original state includes executing a GET request.

### Claim 20 (depends on 18)

The computer-readable medium of claim 18, wherein the changing the web resource to the modified state includes executing a POST or PUT request.
