Systems and methods for request isolation protection

• US 9,674,277 B1
• Filed: 11/16/2016
• Issued: 06/06/2017
• Est. Priority Date: 04/10/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Wang, Jue, Hill, Daniel, Gasch, Scott
• Primary Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US15/353,059
• Time in Patent Office: 202 Days
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: H04L 47/803 Application aware
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Systems and methods for request isolation protection at a first server. The first server receives a resource request from a client device. The first server may receive multiple requests from the same client device or other client devices. The first server caches the multiple requests so that only one resource request is made to a second server storing the resource. The first server detects when the client device cancels the request to the resource. In response, the first server cancels the request made to the second server if there are no other requests made to the resource. If there are other requests remaining, then the first server does not cancel the request to the second server.

Claims

1. A method, comprising:

receiving, from a given client application at a first server, a request for a particular resource that is provided by a second server;

determining, by the first server, that a data structure includes an entry indicating that a previous request for the particular resource was received from another client application and is still being processed by the second server;

in response to determining that the data structure includes an entry indicating that the previous request was received from another client application, incrementing, in the data structure by the first server, a reference count that tracks a number of pending requests for the particular resource without sending a second request for the particular resource to the second server;

receiving, by the first server, a cancellation of a previously received pending request for the particular resource prior to delivery of the particular resource in response to the previously received pending request;

in response to receiving the cancellation, decrementing, in the data structure by the first server, the reference count that tracks the number of pending requests for the particular resource without cancelling the request; and

managing, by the first server, a status of the previous request for the particular resource, including cancelling the previous request for the particular resource prior to the second server providing the particular resource when the reference count indicates that all pending requests for the particular resource have been cancelled.

2. The method of claim 1, wherein the request and the previous request are both from a same client device.

3. The method of claim 2, wherein a user interface of the client device includes a web browser, and wherein receiving the cancellation includes receiving, by the first server, the cancellation of the previously received pending request from the client device that is detected by the web browser.

4. The method of claim 2, wherein determining that the data structure includes an entry indicating that the previous request was received from another client application further comprises:

storing, for each of the request and the previous request in a first data structure provided by the first server, an entry identifying the client device and including a reference to an entry of a second data structure; and

storing, for the request and in the entry in second data structure, an identifier of the request and the reference count.

5. The method of claim 2, wherein receiving the includes receiving the cancellation from the client device after a set amount of time.

6. The method of claim 5, wherein the set amount of time is based on at least one of a predicted popularity of the particular resource, a freshness requirement of the particular resource, an amount of load on the second server, and a size of the request.

7. The method of claim 3, wherein the detection of the cancellation by the web browser includes detecting one of the web browser closing, the web browser stopping of a loading of the particular resource, and the web browser navigating away from the particular resource.

8. The method of claim 7, further comprising receiving, by the first server, another request for the particular resource in response to reloading of the particular resource by the web browser.

9. The method of claim 1, wherein managing the status of the previous request of the particular resource includes detecting that the reference count is zero.

10. A system comprising:

one or more computers and one or more storage devices storing instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising;

receiving, from a given client application at a first server, a request for a particular resource that is provided by a second server;

determining, by the first server, that a data structure includes an entry indicating that a previous request for the particular resource was received from another client application and is still being processed by the second server;

in response to determining that the data structure includes an entry indicating that the previous request was received from another client application, incrementing, in the data structure by the first server, a reference count that tracks a number of pending requests for the particular resource without sending a second request for the particular resource to the second server;

receiving, by the first server, a cancellation of a previously received pending request for the particular resource prior to delivery of the particular resource in response to the previously received pending request;

in response to receiving the cancellation, decrementing, in the data structure by the first server, the reference count that tracks the number of pending requests for the particular resource without cancelling the request; and

managing, by the first server, a status of the previous request for the particular resource, including cancelling the previous request for the particular resource prior to the second server providing the particular resource when the reference count indicates that all pending requests for the particular resource have been cancelled.

11. The system of claim 10, wherein the request and the previous request are both from a same client device.

12. The system of claim 11, wherein a user interface of the client device includes a web browser, and wherein receiving the cancellation includes receiving, by the first server, the cancellation of the previously received pending request from the client device that is detected by the web browser.

13. The system of claim 11, wherein determining that the data structure includes an entry indicating that the previous request was received from another client application further comprises:

storing, for each of the request and the previous request in a first data structure provided by the first server, an entry identifying the client device and including a reference to an entry of a second data structure; and

storing, for the request and in the entry in second data structure, an identifier of the request and the reference count.

14. The system of claim 11, wherein receiving the includes receiving the cancellation from the client device after a set amount of time.

15. The system of claim 14, wherein the set amount of time is based on at least one of a predicted popularity of the particular resource, a freshness requirement of the particular resource, an amount of load on the second server, and a size of the request.

16. The system of claim 12, wherein the detection of the cancellation by the web browser includes detecting one of the web browser closing, the web browser stopping of a loading of the particular resource, and the web browser navigating away from the particular resource.

17. The system of claim 16, the operations further comprising receiving, by the first server, another request for the particular resource in response to reloading of the particular resource by the web browser.

18. A non-transitory computer-readable medium storing software comprising instructions executable by one or more computers which, upon such execution, cause the one or more computers to perform operations comprising:

receiving, from a given client application at a first server, a request for a particular resource that is provided by a second server;

determining, by the first server, that a data structure includes an entry indicating that a previous request for the particular resource was received from another client application and is still being processed by the second server;

in response to determining that the data structure includes an entry indicating that the previous request was received from another client application, incrementing, in the data structure by the first server, a reference count that tracks a number of pending requests for the particular resource without sending a second request for the particular resource to the second server;

receiving, by the first server, a cancellation of a previously received pending request for the particular resource prior to delivery of the particular resource in response to the previously received pending request;

in response to receiving the cancellation, decrementing, in the data structure by the first server, the reference count that tracks the number of pending requests for the particular resource without cancelling the request; and

managing, by the first server, a status of the previous request for the particular resource, including cancelling the previous request for the particular resource prior to the second server providing the particular resource when the reference count indicates that all pending requests for the particular resource have been cancelled.

19. The computer-readable medium of claim 18, wherein the request and the previous request are both from a same client device.

20. The computer-readable medium of claim 19, wherein a user interface of the client device includes a web browser, and wherein receiving the cancellation includes receiving, by the first server, the cancellation of the previously received pending request from the client device that is detected by the web browser.