# US 2019/0095179 A1 · State management persistence

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

- Number: US 2019/0095179 A1
- Document ID: US20190095179A1
- Status: Published application
- Kind: A1
- Application number: 16/003,023
- Filed: 2018-06-07
- Published: 2019-03-28
- Earliest claimed: 2017-09-28
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Christian Straub
- Web page: https://patentgrep.com/patent/US20190095179A1

## CPC

- G06F 8/38: for implementing user interfaces
- G06F 3/0481: based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F 3/0483: Interaction with page-structured environments, e.g. book metaphor
- G06F 8/34: Graphical or visual programming
- G06F 9/4493: {Object persistence}
- G06F 9/451: Execution arrangements for user interfaces
- G06F 16/182: Distributed file systems
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- G06F 3/04817: using icons (graphical or visual programming using iconic symbols G06F8/34)
- G06F 3/0486: Drag-and-drop
- G06F 16/955: using information identifiers, e.g. uniform resource locators [URL]
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A hierarchy of containers is received at a user interface of a design time tool. The hierarchy of containers includes a container nested inside of one or more other containers. Each of the containers includes a different part of a web client application. The design time tool associates state with each of the containers in the hierarchy of containers. Lifecycles for each of the containers are received at the user interface. The design time tool creates computer executable instructions in the web client application that enable state for each of the containers to be created and destroyed according to the hierarchy based on the respective lifecycles of each of the containers. The design time tool provides each of the containers access to its own state and state of containers that include it based on respective lifecycle events associated with each of the containers.

## Claims

### Claim 1

A non-transitory processor-readable storage device including instructions for a method of providing state management persistence, the method comprising:
receiving, at a user interface of a design time tool, a hierarchy of containers with a container nested inside of one or more other containers, wherein each of the containers includes a different part of a web client application;
associating, performed at the design time tool, state with each of the containers in the hierarchy of containers;
receiving, at the user interface of the design time tool, lifecycles for each of the containers;
creating, performed by the design time tool, computer executable instructions for the web client application that enable state for each of the containers to be created and destroyed according to the hierarchy based on the respective lifecycles of each of the containers; and
providing, performed at the design time tool, each of the containers access to its own state and state of containers that include it based on respective lifecycle events associated with each of the containers.

### Claim 2 (depends on 1)

The non-transitory processor-readable storage device as recited by claim 1, wherein the method further comprises:
receiving, at the user interface, specification of a first event in a first lifecycle for a first container;
associating the first event with creation of state for the first container;
receiving, at the user interface, specification of a second event in a second lifecycle of a second container; and
associating the second event with creation of state for the second container.

### Claim 3 (depends on 2)

The non-transitory processor-readable storage device as recited by claim 2, wherein the first event and the second event are different types of events.

### Claim 4 (depends on 1)

The non-transitory processor-readable storage device as recited by claim 1, wherein the method further comprises:
receiving, at the user interface, specification of a first event in a first lifecycle for a first container;
associating the first event with destruction of state for the first container;
receiving, at the user interface, specification of a second event in a second lifecycle of a second container; and
associating the second event with destruction of state for the second container.

### Claim 5 (depends on 4)

The non-transitory processor-readable storage device as recited by claim 4, wherein the first event and the second event are different types of events.

### Claim 6 (depends on 1)

The non-transitory processor-readable storage device as recited by claim 1, wherein the method further comprises:
in response to navigating from a first container to a second container during runtime of the web client application, wherein both the first container and the second container are included in a third container, wherein the navigating triggers a lifecycle event for the first container,
destroying state of the first container; and
preserving state of the third container;
creating state of the second container; and
providing the second container access to the preserved state of the third container.

### Claim 7 (depends on 1)

The non-transitory processor-readable storage device as recited by claim 1, wherein the method further comprises:
associating the containers with parts of a uniform resource locator (URL) pattern, wherein each part of the URL pattern is associated with one of the containers.

### Claim 8 (depends on 7)

The non-transitory processor-readable storage device as recited by claim 7, wherein each of the parts of the URL pattern maintain respective ones of the lifecycles.

### Claim 9 (depends on 7)

The non-transitory processor-readable storage device as recited by claim 7, wherein the method further comprises:
executing a subset of the containers in accordance with a hierarchy paths associated with the URL pattern;
creating variables for containers based on the URL pattern; and
destroying variables for the containers based on the URL pattern.

### Claim 10 (depends on 9)

The non-transitory processor-readable storage device as recited by claim 9, wherein the method further comprises:
providing a particular container access to variables of the particular container and to variables for containers that include the particular container according to a hierarchy path for the particular container.

### Claim 11

A method of providing state management persistence, the method comprising:
receiving, at a user interface of a design time tool, a hierarchy of containers with a container nested inside of one or more other containers, wherein each of the containers includes a different part of a web client application;
associating, performed at the design time tool, state with each of the containers in the hierarchy of containers;
receiving, at the user interface of the design time tool, lifecycles for each of the containers;
creating, performed by the design time tool, computer executable instructions for the web client application that enable state for each of the containers to be created and destroyed according to the hierarchy based on the respective lifecycles of each of the containers; and
providing, performed at the design time tool, each of the containers access to its own state and state of containers that include it based on respective lifecycle events associated with each of the containers.

### Claim 12 (depends on 11)

The method as recited by claim 11, wherein the method further comprises:
receiving, at the user interface, specification of a first event in a first lifecycle for a first container;
associating the first event with creation of state for the first container;
receiving, at the user interface, specification of a second event in a second lifecycle of a second container; and
associating the second event with creation of state for the second container.

### Claim 13 (depends on 12)

The method as recited by claim 12, wherein the first event and the second event are different types of events.

### Claim 14 (depends on 11)

The method as recited by claim 11, wherein the method further comprises:
receiving, at the user interface, specification of a first event in a first lifecycle for a first container;
associating the first event with destruction of state for the first container;
receiving, at the user interface, specification of a second event in a second lifecycle of a second container; and
associating the second event with destruction of state for the second container.

### Claim 15 (depends on 14)

The method as recited by claim 14, wherein the first event and the second event are different types of events.

### Claim 16 (depends on 11)

The method as recited by claim 11, wherein the method further comprises:
in response to navigating from a first container to a second container during runtime of the web client application, wherein both the first container and the second container are included in a third container, wherein the navigating triggers a lifecycle event for the first container,
destroying state of the first container;
preserving state of the third container;
creating state of the second container; and
providing the second container access to the preserved state of the third container.

### Claim 17 (depends on 11)

The method as recited by claim 11, wherein the method further comprises:
associating the containers with parts of a uniform resource locator (URL) pattern, wherein each part of the URL pattern is associated with one of the containers.

### Claim 18 (depends on 17)

The method as recited by claim 17, wherein each of the parts of the URL pattern maintain respective ones of the lifecycles.

### Claim 19 (depends on 17)

The method as recited by claim 17, wherein the method further comprises:
executing a subset of the containers in accordance with a hierarchy paths associated with the URL pattern;
creating variables for containers based on the URL pattern; and
destroying variables for the containers based on the URL pattern.

### Claim 20

A design time tool that provides state management persistence, comprising:
one or more processors; and
a non-transitory processor-readable storage device including instructions for:
receiving, at a user interface of the design time tool, a hierarchy of containers with a container nested inside of one or more other containers, wherein each of the containers includes a different part of a web client application;
associating, performed at the design time tool, state with each of the containers in the hierarchy of containers;
receiving, at the user interface of the design time tool, lifecycles for each of the containers;
creating, performed by the design time tool, computer executable instructions for the web client application that enable state for each of the containers to be created and destroyed according to the hierarchy based on the respective lifecycles of each of the containers; and
providing, performed at the design time tool, each of the containers access to its own state and state of containers that include it based on respective lifecycle events associated with each of the containers.
