Systems and methods for request isolation protection

• US 9,531,839 B1
• Filed: 04/10/2014
• Issued: 12/27/2016
• Est. Priority Date: 04/10/2014
• Status: Expired due to Fees

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Hill, Daniel, Gasch, Scott, Wang, Jue
• Primary Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US14/249,804
• Time in Patent Office: 992 Days
• US Class Current: 1/1
• 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 computer-implemented method for request isolation protection, comprising:

receiving, at a first server, first and second requests that are each for a resource stored in a second server, wherein the first and second requests are both sent from a client device comprising a user interface;

transmitting, by the first server, the first and second requests for the resource to the second server;

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

storing, for the first request and in the entry in the second data structure stored in the memory element, an identifier of the transmitted request and a reference count;

identifying, based on the second request, the entry and incrementing the reference count;

receiving, at the first server, a cancellation of the first request, the cancellation sent from the client device and submitted through the user interface;

in response to receiving the cancellation of the first request at the first server, decrementing, by the first server, the reference count of the entry to provide an updated reference count;

receiving, at the first server, a cancellation of the second request, the cancellation sent from the client device and submitted through the user interface;

in response to receiving the cancellation of the second request, decrementing, by the first server, the updated reference count;

detecting, by the first server, that the updated reference count equals zero; and

in response to detecting the updated reference count equals zero, cancelling, by the first server, the transmitted request for the resource associated with the first and second requests.

2. The method of claim 1, wherein

the user interface comprises a web browser, and

wherein receiving the cancellation comprises receiving, at the first server, the cancellation of the first request, the cancellation sent from the client device and detected by the web browser.

3. The method of claim 2, wherein receiving the cancellation of the first request comprises receiving, at the first server, the cancellation of the first request, the cancellation sent from the client device and detected by the web browser detecting one of:

the web browser closing;

the web browser stopping a loading of the resource; and

the web browser navigating away from the resource.

4. The method of claim 3, wherein receiving cancellation of the first request further comprises:

receiving, at the first server, a third request for the resource, the third request sent from the client device and the web browser reloading the resource.

5. The method of claim 1, wherein cancelling the transmitted request comprises:

cancelling the transmitted request responsive to determining that the transmitted request is still in progress.

6. The method of claim 1, further comprising:

sending, from the second server, the transmitted request for the resource to a third server;

cancelling, at the second server, the request for the resource from the third server, responsive to determining that the transmitted request is cancelled; and

wherein the resource is stored in the third server and the memory element is provided by the second server.

7. The method of claim 1, wherein cancelling the transmitted request comprises:

cancelling the transmitted request after a set amount of time.

8. The method of claim 7, wherein cancelling the transmitted request comprises:

receiving, at the first server, a third request for the resource within a set amount of time after detecting that the second table entry has a reference count of zero, the third request sent from a second client device comprising a second user interface;

storing, in the first data structure stored in the memory element provided by the first server, a new entry identifying the second client device and including a reference to the entry of the second data structure;

receiving, at the first server, a cancellation of the third request, the cancellation sent from the second client device and detected by the second user interface;

decrementing the reference count of the second table entry;

detecting that the second table entry has a reference count of zero; and

cancelling the transmitted request after a set amount of time.

9. The method of claim 7, further comprising determining the set amount of time based on one of:

a predicted popularity of the resource;

a freshness requirement of the resource;

an amount of load on the second server;

or

a size of the request.

10. The method of claim 1, wherein the first data structure and the second data structure are implemented as a multimap.

11. A system for request isolation protection, comprising:

a second server storing a resource;

a first server, comprising;

a receiver receiving first and second requests that are each for the resource, wherein the first and second requests are both sent from a client device comprising a user interface;

a transmitter transmitting the first and second requests for the resource to the second server;

a memory element storing;

a first data structure comprising an entry, for each of the first and the second requests, identifying the client device and including a reference to an entry of a second data structure; and

a second data structure comprising the entry, for the first request, comprising an identifier of the transmitted request, and a reference count;

a detector receiving;

a cancellation of the first request, the cancellation sent from the client device and submitted through the user interface;

a cancellation of the second request, the cancellation sent from the client device and submitted through the user interface;

a controller, connected to the memory element;

identifying, based on the second request, the entry and incrementing the reference count;

decrementing, in response to receiving the cancellation of the first request, the reference count of the entry in the second data structure to provide an updated reference count;

decrementing, in response to receiving the cancellation of the second request, the updated reference count;

detecting that the updated reference count equals zero; and

cancelling, in response to detecting the updated reference count equals zero, the transmitted request for the resource associated with the first and second requests.

12. The system of claim 11, wherein the user interface comprises a web browser.

13. The system of claim 12, wherein the detector is further configured to receive the cancellation of the first request sent from the client device and submitted through the web browser detecting one of:

the web browser closing;

the web browser stopping a loading of the resource; and

the web browser navigating away from the resource.

14. The system of claim 13, wherein the receiver is further configured to receive a third request for the resource, the third request sent from the client device and the web browser reloading the resource.

15. The system of claim 11, wherein the controller is configured to cancel the transmitted request responsive to determining that the transmitted request is still in progress.

16. The system of claim 11, further comprising:

a third server storing the resource; and

wherein the second server provides the memory element and is configured to request the resource from the third server, and cancel the request for the resource from the third server, responsive to determining that the transmitted request is cancelled.

17. The system of claim 11, wherein the controller is configured to cancel the transmitted request after a set amount of time.

18. The system of claim 17, wherein the receiver is further configured to

receive a third request for the resource within a set amount of time after detecting that the second table entry has a reference count of zero, the third request sent from a second client device comprising a second user interface;

and

wherein the detector is further configured to

receive a cancellation of the third request, the cancellation sent from the second client device and detected by the second user interface;

wherein the memory element is further configured to

store, in the first data structure, a new entry identifying the second client device and including a reference to the entry of the second data structure; and

wherein the controller is further configured to;

decrement the reference count of the second table entry;

detect that the second table entry has a reference count of zero; and

cancel the transmitted request after a set amount of time.

19. The system of claim 17, the controller is further configured to determine the set amount of time based on one of:

a predicted popularity of the resource;

a freshness requirement of the resource;

an amount of load on the second server;

or

a size of the request.

20. The system of claim 11, wherein the first data structure and the second data structure are implemented as a multimap.