Rules-based transaction prefetching using connection end-point proxies

• US 7,853,699 B2
• Filed: 11/14/2005
• Issued: 12/14/2010
• Est. Priority Date: 03/15/2005
• Status: Active Grant

• Current Assignee: Riverbed Technology, LLC (Riverbed Technology Incorporated)
• Original Assignee: Riverbed Technology Incorporated
• Inventors: Wu, David Tze-Si, Keswani, Vivasvat, Larsen, Case
• Primary Examiner(s): BARQADLE, YASIN M
• Application Number:
  US11/273,861
• Publication Number:
  US 20060212524A1
• Time in Patent Office: 1,856 Days
• Field of Search: 709201-206, 709217-229
• US Class Current: 709/227
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• 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/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Network proxies reduce server latency in response to series of requests from client applications. Network proxies intercept messages clients and a server. Intercepted client requests are compared with rules. When client requests match a rule, additional request messages are forwarded to the server on behalf of a client application. In response to the additional request messages, the server provides corresponding response messages. A network proxy intercepts and caches the response messages. Subsequent client requests are intercepted by the network application proxy and compared with the cached messages. If a cached response message corresponds with a client request message, the response message is returned to the client application immediately instead of re-requesting the same information from the server. A server-side network proxy can compare client requests with the rules and send additional request messages. The corresponding response messages can be forwarded to a client-side network proxy for caching.

Claims

1. A method for accelerating a client-server transaction, the method comprising:

(a) receiving, at a proxy, a first message from a client application, wherein the proxy is distinct from a client executing the client application;

(b) comparing, at the proxy, the first message with a set of rules, and determining whether the first message invalidates previously fetched responses;

(c) forwarding the first message from the proxy to a server application executed by a server and forwarding at least one additional message from the proxy to the server application on the server in response to the first message matching at least one of the set of rules, wherein the at least one additional message is determined at the proxy based on content of the first message and the set of rules applied to the content of the first message and wherein the at least one additional message is creatable in advance of receipt of a response to the first message;

(d) receiving, at the proxy, from the server application at least one response message corresponding with the additional message;

(e) storing in a message cache the response message corresponding with the additional message such that the cached response message remains associated with the additional message;

(f) receiving a second message from the client application;

(g) determining if the second message is similar to the additional message; and

(h) forwarding the response message stored in the message cache to the client application as a response to the second message in response to the second message being similar to the additional message.

2. The method of claim 1, wherein the proxy is a server-side network proxy and (e), (f), (g), and (h) are performed by a client-side network proxy.

3. The method of claim 2, wherein (e) further comprises:

sending the at least one response message from the server-side network proxy to the client-side network proxy.

4. The method of claim 3, wherein sending the response message further comprises wrapping the response message with additional information adapted to indicate to the client-side network proxy that the response message is to be stored in the message cache.

5. The method of claim 4, wherein the additional information identifies the additional message corresponding with the response message.

6. The method of claim 3, further comprising:

in response to (e), determining if a cache limit has been reached;

sending, by the client-side proxy, a throttling message to the server-side proxy in response to a determination that the cache limit has been reached; and

suspending the sending of at least one response message from the server-side network proxy to the client-side network proxy in response to the server-side network proxy receiving the throttling message.

7. The method of claim 6, further comprising, in response to (h):

removing the forwarded response message from the response cache;

determining if the cache storage limit has been reached;

sending by the client-side proxy, an un-throttling message to the server-side proxy in response to a determination the cache storage limit has not been reached; and

resuming the sending of at least one response message from the server-side network proxy to the client-side network proxy in response to the server-side network proxy receiving the un-throttling message.

8. The method of claim 1, further comprising:

generating a preacknowledgment message corresponding with the first message; and

forwarding the preacknowledgment message to the client application.

9. The method of claim 8, further comprising:

receiving an acknowledgment message from the server application, wherein the acknowledgment message is a response to the first message;

analyzing a status code of the acknowledgment message;

discarding the acknowledgment message in response to the status code indicating a success condition; and

forwarding a response message indicating a failure condition to the client application following the receipt of the second message from the client application in response to the status code of the acknowledgment message indicating a failure condition.

10. The method of claim 1, wherein the proxy comprises a server side network proxy.

11. The method of claim 1, wherein the proxy comprises a client-side network proxy.

12. The method of claim 1, wherein (b) further comprises:

relaying a result of the determining to the message cache, which purges all or part of the previously fetched responses based on the result.