Managing identical data requests

• US 10,063,657 B2
• Filed: 10/13/2015
• Issued: 08/28/2018
• Est. Priority Date: 10/13/2015
• Status: Active Grant

• Current Assignee: Sap Portals Israel Ltd (SAP SE)
• Original Assignee: Sap Portals Israel Ltd (SAP SE)
• Inventors: Vulich, Yan
• Primary Examiner(s): Anyan, Barbara B
• Application Number:
  US14/881,405
• Publication Number:
  US 20170104846A1
• Time in Patent Office: 1,050 Days
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

The disclosure generally describes methods, software, and systems, including a method for managing co-pending, identical data requests. An initial request is received for a first data object. Processing of the initial request is initiated, including dispatching the initial request to a server. Prior to receiving a response to the dispatched initial request, a first identical request is received. The first identical request is held without dispatching. Prior to receiving the response to the dispatched initial request, a second identical request is received. The first identical request is disregarded and the second identical request is held without dispatching the second identical request to the server. The responsive data object is received in response to the initial request. The responsive data object is provided in response to the second identical request, the providing occurring without initiating processing, by the server, of the first identical request and the second identical request.

Claims

1. A computer-implemented method, the method comprising:

receiving, at a dispatcher associated with a server, an initial request for performing processing associated with a first data object from a first client;

dispatching, by the dispatcher, the initial request to the server to initiate the processing associated with the first data object;

receiving, at the dispatcher and from the first client, and prior to the dispatcher receiving a response to the initial request from the server corresponding to the processing associated with the first data object, a second request for the processing associated with the first data object identical to the initial request from the first client;

in response to determining that the second request is identical to the initial request and prior to the dispatcher receiving the response from the server to the initial request from the first client, holding, by the dispatcher, the second request without dispatching the second request to the server and without transmitting a response to the initial request or the second request to the first client;

receiving, at the dispatcher and from the first client, prior to receiving the response to the initial request corresponding to the processing associated with the first data object, and after receiving the second request from the first client, a third request for the processing associated with the first data object, the third request identical to the initial request and the second request;

in response to determining that the third request is identical to the initial request and the second request, and prior to receiving the response to the initial request from the server, discarding the second request and holding the third request without dispatching the third request to the server and without transmitting a response to the initial request, the second request, or the third request to the first client;

receiving, from the server, at the dispatcher, and in response to the initial request, the response to the initial request corresponding to the processing associated with the first data object; and

in response to receiving the response from the server;

associating the received response with the currently held third request; and

transmitting the response to the first client in response to the third request, the transmitting occurring without dispatching, by the dispatcher, the second request and the third request to the server or responses to the initial or second request to the first client.

2. The method of claim 1, wherein the server is, or includes, one or more of a web server and an application.

3. The method of claim 1, wherein the initial request, the second request, and the third request are from the same user at the first client.

4. The method of claim 1, further comprising:

sending, by the dispatcher, a notification to the first client in response to determining that a new request is identical to a previously received request, wherein the notification includes an indication that a prior identical request was received and a request to a user associated with the first client to choose between waiting for a response to the initial request or processing the new request separately from the initial request.

5. The method of claim 1, wherein the first data object is a business object.

6. A system comprising:

at least one processor;

a memory storing;

a data store of received requests; and

an application operable when executed by the at least one processor to perform operations comprising;

receiving, from a first client, an initial request for performing processing associated with a first data object;

dispatching the received initial request to a server to initiate the processing associated with the first data object;

while waiting to receive a response to the dispatched initial request corresponding to the first data object from the server;

receiving, from the first client, by the application and prior to receiving the response to the initial request from the server corresponding to the processing associated with the first data object, at least one identical request for processing associated with the first data object identical to the initial request from the first client;

determining that the at least one identical request is identical to the initial request; and

holding the most recently received at least one identical request without dispatching any of the previously-received at least one identical requests to the server and discarding the previously-received at least one identical requests; and

receiving, from the server in response to the initial request, the response to the initial request corresponding to the processing associated with the first data object; and

in response to receiving the response to the initial request from the server;

associating the received response with the most recently received identical request; and

transmitting, to the first client, the response to the first client to the most recently received of the at least one identical requests to the first client, the transmitting occurring without dispatching any of the at least one identical requests to the server.

7. The system of claim 6, wherein the server is, or includes, one or more of a web server and an application.

8. The system of claim 6, wherein the initial request and the each of the at least one identical requests are from the same user of the first client.

9. The system of claim 6, the operations further comprising:

sending, by the application, a notification to the first client in response to determining that a new request is identical to a previously received request while waiting to receive a response to the initial request from the server.

10. The system of claim 6, wherein the first data object is a business object.

11. A non-transitory computer-readable media encoded with a computer program, the program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:

receiving, at a dispatcher associated with a server and from a first client, an initial request for performing processing associated with a first data object;

dispatching, by the dispatcher, the initial request to the server to initiate the processing associated with the first data object;

receiving, at the dispatcher and from the first client, and prior to the dispatcher receiving a response to the initial request from the server corresponding to processing associated with the first data object, a second request for processing associated with the first data object identical to the initial request from the first client;

in response to determining that the second request is identical to the initial request and prior to the dispatcher receiving the response to the initial response from the first client, holding the second request without dispatching the second request to the server and without transmitting a response to the initial request or the second request to the first client;

receiving, at the dispatcher and from the first client, prior to receiving the response to the initial request corresponding to the processing associated with the first data object, and after receiving the second request from the first client, a third request for the processing associated with the first data object, the third request identical to the initial request and the second request;

in response to determining that the third request is identical to the initial request and the second request, and prior to receiving the response to the initial request from the server, discarding the second request and holding the third request without dispatching the third request to the server and without transmitting a response to the initial request, the second request, or the third request to the first client;

receiving, from the server, at the dispatcher, and in response to the initial request, the response to the initial request corresponding to the processing associated with the first data object; and

in response to receiving the response from the server;

associating the received response with the currently held third request; and

transmitting the response to the first client in response to the third request, the transmitting occurring without dispatching, by the dispatcher, the second request and the third request to the server or responses to the initial or second request to the first client.

12. The non-transitory computer-readable media of claim 11, wherein the server is, or includes, one or more of a web server and an application.

13. The non-transitory computer-readable media of claim 11, wherein the initial request, the second request, and the third request are from the same user at the first client.

14. The non-transitory computer-readable media of claim 11, the operations further comprising:

sending, by the dispatcher, a notification to the first client in response to determining that a new request is identical to a previously received request.