Systems and methods for request isolation protection
First Claim
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 Assignments
0 Petitions
Accused Products
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.
22 Citations
20 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
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. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification