RAPID CLIENT-SIDE COMPONENT PROCESSING BASED ON COMPONENT RELATIONSHIPS

• US 20120023154A1
• Filed: 07/22/2010
• Published: 01/26/2012
• Est. Priority Date: 07/22/2010
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Demant, Hilmar, Droll, Sebastian, Fitzer, Joachim, Grammatikakis, Ioannis, Heiler, Jan, Sattler, Juergen, Schertel, Frank, Viol, Markus, Weber, Thorsten
• Granted Patent: US 9,491,238 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: 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]
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A client database manager can cause a memory of a client device on a client side of a network to store a first component, a second component, and a relationship value representing a dependent relationship between the first component and the second component. A client processing module can cause a processor to receive, after the storing, a request to process the first component at the client device. The client database manager can send to the server side of the network a request for an update of at least one of the first component or the second component. The client processing module can cause the processor to process at the client device, before receiving a response to the request for the update from the server side of the network, at least a portion of the first component and at least a portion of the second component based on the relationship value.

Claims

1. A computer system including instructions stored on a non-transitory computer-readable storage medium, the computer system comprising:

a client database manager configured to cause a memory of a client device on a client side of a network to store a first component, a second component, and a relationship value representing a dependent relationship between the first component and the second component; and

a client processing module configured to cause a processor to receive, after the storing, a request to process the first component at the client device,

the client database manager configured to send to the server side of the network, in response to the request to process the first component, a request for an update of at least one of the first component or the second component,

the client processing module configured to cause the processor to process at the client device, in response to the request to process the first component and before receiving a response to the request for the update from the server side of the network, at least a portion of the first component and at least a portion of the second component based on the relationship value.

2. The computer system of claim 1, wherein the relationship value includes a first relationship value and the dependent relationship includes a first dependent relationship,

the client database manager is configured to retrieve, in response to the request to process the first component, a third component based on a second relationship value representing a second dependent relationship between the third component and the first component,

the client processing module is configured to cause the processor to process, before receiving the response to the request for the update from the server side of the network, at least a portion of the third component.

3. The computer system of claim 1, wherein the dependent relationship includes a first dependent relationship,

the client processing module is configured to cause the processor to process, in response to the request to process the first component, at least a portion of a third component having a dependent relationship with the second component such that the first component, the second component, and the third component are hierachically related.

4. The computer system of claim 1, wherein the dependent relationship includes a first dependent relationship,

the client processing module is configured to cause the processor to process, in response to the request to process the first component, at least a portion of a third component having a second dependent relationship with the second component,

the client processing module is configured to cause the processor to start processing of the portion of the second component before the client processing module causes the processor to start processing of the portion of the third component when the first dependent relationship has a priority higher than a priority of the second dependent relationship.

5. The computer system of claim 1, wherein:

the client database manager is configured to cause the memory of the client device to store a plurality of components, which includes at least the first component and the second component, in a component database of the client device,

the client database manager is configured to cause the memory of the client device to store a plurality of relationship values, which includes the relationship value, in a relationship metadata database of the client device,

the client database manager is configured to maintain the relationship metadata database of the client device and the component database of the client device so that the relationship metadata database of the client device and the component database of the client device mirror, respectively, a subset of a relationship metadata database on the server side of the network and a subset of a component database on the server side of the network.

6. The computer system of claim 1, wherein the first component includes a first user-interface component and the second component includes a second user-interface component.

7. The computer system of claim 1, wherein the dependent relationship includes a first dependent relationship,

the client database manager is configured to identify a second dependent relationship between a third component and at least one of the first component or the second component,

the client database manager is configured to send to the server side of the network a request for an update of the third component,

the sending of the request for the update of the third component is performed by the client database manager after the sending of the request for the update of the at least one of the first component or the second component when the first dependent relationship has a priority higher than a priority of the second dependent relationship.

8. The computer system of claim 1, wherein the request for the update includes state information representing a state of the dependent relationship between the first component and the second component and an index value that is a pointer to at least one of the first component or the second component.

9. The computer system of claim 1, wherein:

the client database manager is configured to receive an updated second component in response to the request for the update,

the client processing module is configured to cause, in response to receipt of the updated second component, the processor to terminate processing of the first component and the second component, and cause the processor to process at least a portion of the first component and at least a portion of the updated second component.

10. The computer system of claim 1, wherein the client database manager is configured to send the request for the update in conjunction with the client processing module causing the processor to process the at least the portion of the first component and the at least the portion of the second component.

11. The computer system of claim 1, wherein the client database manager is configured to send the request for the update after the client processing module causes the processor to process the at least the portion of the first component and the at least the portion of the second component.

12. The computer system of claim 1, where the dependent relationship between the first component and the second component is defined such that the second component is triggered for processing only after at least a portion of the first component has been processed.

13. The system of claim 1, wherein:

the dependent relationship includes a nested dependent relationship; and

the memory of the client device includes a multi-level memory.

14. A non-transitory computer-readable storage medium storing code representing instructions that when executed are configured to cause a processor to perform a process, the code comprising code to:

receive a request to process a component at a client device on a client side of a network;

send, to a server device on a server side of the network, a request to retrieve the component;

receive, in response to the request to retrieve the component, a plurality of relationship values and a plurality of components including the component, each relationship value from the plurality of relationship values representing at least a portion of a dependent relationship between one component from the plurality of components and another component from the plurality of components; and

store the plurality of relationship values in a relationship metadata database in a memory of the client device, the relationship metadata database at the client device mirroring at least a portion of a relationship metadata database maintained at the server device.

15. The non-transitory computer-readable storage medium of claim 14, wherein the request to process the component is a first request to process the component, the first request is received at a first time at the client device,

the code further comprising code to:

access the plurality of relationship values in response to a second request to process the component, the second request being received at the client device at a second time after the first time, the plurality of relationship values representing a set of hierarchical relationships between the component and the remaining components from the plurality of components;

send to the server side of the network, in response to the second request to process the component, a request for an update of at least a portion of at least one of the plurality of relationship values or the plurality of components; and

trigger, before a response to the request for the update is received, processing of at least a portion of the remaining components from the plurality of components at the client device based on at least a portion of the plurality of relationship values.

16. The non-transitory computer-readable storage medium of claim 14, wherein the request to process the component is a first request to process the component,

the code further comprising code to:

trigger, starting at a time, processing of the plurality of components at the client device in an order based on the plurality of relationship values after the storing of the plurality of relationship values in the relationship metadata database of the client device;

receive, after the time, a second request to process the component at the client device;

trigger, in response to the second request to process the component, processing of the plurality of components at the client device in the order based on the plurality of relationship values stored in the relationship metadata database of the client device;

send to the server side of the network, in response to the second request to process the component, a request for an update of at least a portion of at least one of the plurality of relationship values or the plurality of components;

receive a response to the request for the update; and

trigger re-processing of a portion of the plurality of components based on the response.

17. The non-transitory computer-readable storage medium of claim 14, wherein the request to process the component is a first request to process the component,

the code further comprising code to:

store the plurality of components in the memory of the client device in a component database;

trigger, in response to a second request to process the component, processing of the plurality of components at the client device in an order defined based on the plurality of relationship values stored in the relationship metadata database of the client device; and

send to the server side of the network, in response to the second request to process the component, a request for an update of at least a portion of at least one of the plurality of relationship values or the plurality of components;

receive a response to the request for the update; and

modify, at the client device and based on the response, at least one of (1) at least a portion of the plurality of components or (2) at least a portion of the plurality of relationship values.

18. A method including executing instructions recorded on a non-transitory computer-readable storage media using at least one processor, the method comprising:

determining a plurality of hierarchical dependencies of a set of subsidiary components with respect to a primary component;

defining on a server side of a network a set of relationship values collectively representing the plurality of hierarchical dependencies of the set of subsidiary components with respect to the primary component;

receiving from the client side of the network a request for the primary component; and

sending to the client side of the network, and in response to the request for the primary component, the primary component, the set of subsidiary components, and the set of relationship values.

19. The method of claim 18, further comprising:

receiving, on the server side of the network, an indicator that at least a portion of the plurality of hierarchical dependencies has changed;

modifying, on the server side of the network, the set of relationship values in response to the change; and

sending, in response to a request for an update from the client side of the network, the modified set of relationship values.

20. The method of claim 18, wherein the determining the plurality of hierarchical dependencies includes iteratively identifying each dependent relationship of each subsidiary component from the set of subsidiary components starting with the primary component.