US20130013673A1 - Meta-data based method for local cache utilization - Google Patents
Meta-data based method for local cache utilization Download PDFInfo
- Publication number
- US20130013673A1 US20130013673A1 US13/615,748 US201213615748A US2013013673A1 US 20130013673 A1 US20130013673 A1 US 20130013673A1 US 201213615748 A US201213615748 A US 201213615748A US 2013013673 A1 US2013013673 A1 US 2013013673A1
- Authority
- US
- United States
- Prior art keywords
- proxy
- client
- data
- server
- response data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000004891 communication Methods 0.000 claims abstract description 9
- 230000004044 response Effects 0.000 claims description 147
- 230000005540 biological transmission Effects 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 3
- 230000009467 reduction Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 101100217298 Mus musculus Aspm gene Proteins 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/2876—Pairs of inter-processing entities at each side of the network, e.g. split proxies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- the present invention relates to a method (named Meta-Data Based Caching, or MDBC) of caching data locally by a client while using HTTP protocol for downloading data from a server in order to reduce the volume of data communication and also possibly reduce the data transmission time.
- MDBC Meta-Data Based Caching
- HTTP Hyper Text Transfer Protocol
- the HTTP protocol can be visualized as a protocol for interaction between a HTTP client (or simply called client in this document) that sends requests for data, and a HTTP server (or simply called server in this document) that supplies the data.
- the client after sending the request, waits for the server's response, and then normally, upon receipt of data, delivers the data to the end user.
- the client is implemented by a software component called a web-browser.
- the server is usually implemented by a software component called a web-server.
- HTTP protocol by other types of software components to create a HTTP client or a HTTP server for exchange of data over the Internet.
- the client uses a text string called a Uniform Resource Locater (URL) to identify the data being requested by the client.
- URL Uniform Resource Locater
- the HTTP protocol provides a mechanism for making use of the data previously accessed from the server which may be cached locally by a client.
- Such methods are described in R. Fielding, J. Gettys, J. Mogul, H Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, “Request for Comments: 2616, Hypertext Transfer Protocol—HTTP/1.1,” Network Working Group, June 1999 (“Fielding”), which is hereby incorporated by reference herein.
- the primary benefits of caching data by the client are reduction in the volume of data transmitted by the server to the client, and reduction in the time required for accessing the data by the client.
- a client locally stores or caches a copy of the data corresponding to a URL
- the client's copy of the data corresponding to the URL is considered to be “fresh” or “stale” depending on whether the client's cached copy still contains the valid data or not. If the client's cache does contain a valid copy of the requested data, the client's copy is considered to be “fresh”. On the other hand, if the client's cached copy no longer contains valid data corresponding to the URL, the client's copy is considered to be “stale.
- the HTTP protocol outlined in Fielding essentially relies on one of two metrics to determine if the copy of the content cached at the client is “stale” or “fresh”:
- the origin-server provides an explicit expiration time/date for the data corresponding to the URL.
- the client's caching mechanism maintains a database that maps each named data to its respective expiration time/date. Thus, each time the data is requested, the client's caching mechanism checks the database to see if the data is in the local cache of the client and if the expiration time/date has passed. If the expiration time/date has not passed then the request is fulfilled directly from the local cache and the origin server is not consulted. This technique or method is known as the “expiration” method of cache control.
- Method B differs from Method A in that the origin-server does not explicitly specify an expiration time/date for each object, rather the caching mechanism associated with the client uses its own internal metrics to approximate an expiration date and time.
- Method A is the preferred caching method, and also the more accurate of the two, but it is generally only effective as long as the server's expiration times are carefully chosen. Unfortunately, for a large and complex server with dynamic data, it is almost impossible to know a priori how much time will pass before a specific data will semantically change.
- Method B does not impose any requirements on server's administrators, it is not possible for this method to be perfectly accurate and, as a result, it may compromise semantic transparency.
- caching as described in Fielding has two specific methods for reducing the volume of data transmission during the interaction between a client and a server:
- Method I relies on the origin-server to supply an explicit expiration time/date for the data. According to this method, if the requested data is found in the local cache of the client, and it has not expired, the client need not send the request to the server.
- the origin-server need not provide an expiration date for the data.
- the client's caching mechanism checks its database for a cached version of the requested data. If a cached version is found, then a request is sent to the origin-server to send the data if and only if the requested content has been modified since the time the client cached the data. If the content has not been modified, then the server only sends a response header and thereby instructs the client to use the cached copy. However, if the data has been modified since the last access, the server sends the new data.
- Method I or Method II deals with a situation in which the data has been specified as not being suitable for caching by the server (or administrator thereof). In some situations, it may be simpler or more beneficial for a server to identify all data as not being suitable for caching so that there is no need to calculate/estimate an expiration time/date or other reason. As such, there is a need for a way to allow caching of many types of data, including that which is ordinarily indicated as “no cache”.
- the system and method of the invention builds upon and is intended to improve upon the existing methods described above by providing additional methods for ascertaining the validity of cached data between a client and server, and thus reduce the volume of data transmission requirements.
- the method is based on utilizing computed characteristics, called meta-data, associated with the response data for a particular URL.
- a system for caching data using a client-server model includes: a) a client proxy and a server proxy in communication with each other and with the client and the server, respectively; b) a plurality of processors for calculating client proxy meta-data and server proxy meta-data related to the data cached by the client proxy and server proxy, respectively; and, c) a communication link for communicating said meta-data between the client proxy and the server proxy. At least one processor from the plurality of processors is further configured to compare the client proxy meta-data and the server proxy meta-data to determine a cache hit or miss.
- a method for optimizing the transmission of data from a server to a client comprising the steps of: a) upon a client request for data to a client proxy, determining if a prior version of said data exists in a client proxy cache, if so forwarding a request containing client proxy meta-data describing said prior version of said data to a server proxy; b) if at step a) said prior version of said data does not exist in said client proxy cache, sending a request for said data to said server proxy; c) upon receipt of a request from step a) said server proxy determining if said prior version of said data is current based on comparing said client proxy meta-data with server proxy meta-data describing the data requested, if said prior version of said data is current, informing said client proxy of this, if not then fetching the current data from the said server, returning current data and updating server proxy meta-data; d) upon receipt of a request from step b) fetching current data from said server
- FIG. 1 shows the general structure of a meta-data based system for local cache utilization according to an embodiment of the invention.
- FIG. 2 shows a flowchart of the operation of a meta-data based method for local cache utilization according to an embodiment of the invention.
- the software architecture for the MDBC method of interaction between a HTTP client and HTTP server is shown in FIG. 1 .
- HTTP Client in FIG. 1 represents any HTTP client that requests data from a server using the HTTP protocol.
- HTTP Server component in FIG. 1 represents any HTTP server that supplies data to requesting clients.
- HTTP Client on the client computer does not directly interact with HTTP Server. Rather, two intermediate software components are used—one on the client side, and the other on the server side.
- the client side component is called Client Proxy.
- the server side component is called Server Proxy.
- a Server Proxy can concurrently interact with (or serve) more than one Client Proxy components located on different client computers. Instead of sending its HTTP request for data directly to HTTP Server, HTTP Client sends the data to Client Proxy.
- Client Proxy may modify the original request from HTTP Client and then sends the request to Server Proxy.
- Server Proxy first attempts to respond to Client Proxy's request using its own cached data, failing which it may send the request to HTTP Server.
- HTTP Response from HTTP Server is communicated through the Server Proxy and then to Client Proxy, before being delivered to HTTP Client.
- all the data that is communicated between Client Proxy and Server Proxy can be optimized using a customized protocol between Client Proxy and Server Proxy by using optimization techniques, including but not limited to, data compression techniques.
- HTTP Client may optionally search its own cache and then determine if a valid copy of the required data is present in its own cache or whether a HTTP request for a given URL needs to be sent.
- HTTP Client sends Client Proxy a request of the following form:
- Both Client Proxy and Server Proxy maintain their respective databases that hold, for a certain period of time, additional information about each HTTP response data corresponding to a URL that has previously been received along with the actual response data.
- This additional information is called meta-data associated with the response data.
- This meta-data includes, but is not limited to, the URL associated with the response data, (more generally, the meta-data can be indexed or keyed to the requested URL) the type of data in the response data (for example, a text file, or a GIF image file), the length of the response data, a hash value associated with the response data.
- the hash value could be computed using CRC-16, CRC-32, SHA1, MD2, MD4, MD5, or any other suitable algorithm.
- Client Proxy and Server Proxy are coordinated with respect to the meta-data elements used in a particular implementation of MDBC method and algorithms used for computing each such meta-data element.
- Client Proxy simply forwards HTTP Client's request to Server Proxy.
- Server Proxy first searches its own data cache for the response data for the URL specified by the Client Proxy that is currently valid based on either Expiration Time Method or the Last-Modified Time Method. If such data is found, Server Proxy returns the response data to the Client Proxy. Otherwise, Server Proxy interacts as a regular HTTP client with HTTP Server as described in Fielding and receives the response data from the HTTP Server. Server Proxy sends the response data to Client Proxy. In either case, the Client Proxy, in turn, sends the response data to HTTP Client. Both Client Proxy and Server Proxy cache the response data along with the meta-data in their respective databases for their future use.
- Client Proxy In a case in which, a prior response corresponding to the requested URL is found in Client Proxy's cache, Client Proxy, as part of a modified request, forwards to Server Proxy elements of the meta-data associated with the prior response data for that specific URL.
- Server Proxy upon receiving the request from the Client Proxy, first attempts to fulfill the request from the Client Proxy by examining its own cache. If a prior response data for the particular URL is found in Server Proxy's cache, which is still valid based on either the Expiration Time Method or the Last-Modified Time Method, then Server Proxy retrieves the meta-data for the response data from its cache and compares each element of the newly computed meta-data with the corresponding values of meta-data supplied by Client Proxy. If the values for all the corresponding elements of meta-data match, then the Server Proxy informs the Client Proxy to deliver to HTTP Client the response data that is stored in the Client Proxy's cache. The actual response body is not transmitted from the Server Proxy to Client Proxy. Client Proxy delivers the HTTP response data from the Client Proxy's cache to the HTTP client.
- Server Proxy acts as a HTTP client to the HTTP Server and sends a regular HTTP request based on the protocol described in Fielding to HTTP Server.
- HTTP Server sends the HTTP response data to Server Proxy.
- Server Proxy computes the meta-data for the newly received response data from HTTP Server, using the same algorithm as was used by the Client Proxy, and compares each element of the newly computed meta-data with the corresponding values of meta-data supplied by Client Proxy. If the values for all the corresponding elements of meta-data match, then the Server Proxy informs the Client Proxy to deliver to the HTTP Client the data that is stored in the Client Proxy's cache. The actual response body is not transmitted from the Server Proxy to Client Proxy.
- Server Proxy stores the response data along with the associated URL and meta-data in its own cache.
- Server Proxy on receiving the requested response data either from its own cache or from HTTP Server, computes the meta-data for the newly received response data, and any element of the newly computed meta-data does not match with the corresponding element of the meta-data supplied by the Client Proxy, the cached copy of the response data, stored in Client Proxy's cache, is considered invalid.
- Server Proxy sends the newly received response data to the Client Proxy.
- Client Proxy then sends the response data to HTTP Client.
- Both Client Proxy and Server Proxy cache the new response data in their respective databases along with the associated URL and meta-data for their future use.
- This method may result in a significant reduction in the volume of data transmission from Server Proxy to Client Proxy, and therefore, it may also reduce the time elapsed from the time the request was generated by the HTTP Client and the time the response is delivered to the HTTP Client. It is particularly beneficial when Client Proxy and Server Proxy are connected over a low bandwidth link.
- the caching method according to embodiments of the invention coexists with those techniques described in Fielding, but also handles cases the techniques in Fielding may miss. For instance, even data marked as “Cache-Control: private” or “Cache Control: no-cache” (indicating that the data should not be cached) can be safely cached using the MDBC method according to embodiments of the invention. Also, the meta-data can be used to supplement the methods in Fielding as additional or independent metrics for ascertaining whether a cached copy of response data is valid or not.
- the HTTP Client can achieve a high degree of certainty in receiving the requested data that is correct, and not “stale”.
- Client Proxy uses the length of the response data and a computed hash value as two elements of the meta-data (in addition to the URL string itself) associated with a response data for a URL.
- HTTP Client sends Client Proxy a request of the following form:
- Client Proxy simply forwards HTTP Client's request to Server Proxy.
- Server Proxy first searches its own data cache for the response data for the URL specified by the Client Proxy that is currently valid based on either the Expiration Time Method or Last-Modified Time Method. If such data is found, Proxy Server returns the response data to the Client Proxy. Otherwise, Server Proxy interacts as a regular HTTP client with HTTP Server as described in Fielding and receives the response data from the HTTP Server. Server Proxy sends the response data to Client Proxy. In either case, Client Proxy, in turn, sends the response data to HTTP Client. Both Client Proxy and Server Proxy cache the response data, along with the URL string, length and hash value, in their respective databases for their future use.
- Client Proxy In the case where a prior response corresponding to the requested URL is found in Client Proxy's cache, Client Proxy, as part of a modified request, forwards to Server Proxy the request for the URL along with the length and the hash value of the last response data it received for that specific URL.
- Server Proxy upon receiving the request from the Client Proxy, first attempts to fulfill the request from the Client Proxy by examining its own cache. If a prior response data for the particular URL is found in Server Proxy's cache, which is still valid based on either Expiration Time Method or Last-Modified Time Method, then Server Proxy computes the length and hash value for the response data from its cache, using the same algorithm as was used by the Client Proxy, and compares new length and hash value with the length and hash value respectively supplied by Client Proxy. If the length and hash values both match, Server Proxy informs Client Proxy to deliver HTTP Client the response data that is stored in Client Proxy's cache. The actual body of response data is not transmitted from the Server Proxy to Client Proxy. Client Proxy delivers the HTTP response data from the Client Proxy's cache to the HTTP Client.
- Server Proxy acts as a HTTP client to the HTTP Server and sends a regular HTTP request based on the protocol described in Fielding to HTTP Server.
- HTTP Server sends the HTTP response data to Server Proxy.
- Server Proxy computes the length and hash value for the newly received response data from HTTP Server, using the same algorithm as was used by Client Proxy, and compares the newly computed length and hash value with the values of length and hash value respectively, supplied by Client Proxy.
- the Server Proxy informs the Client Proxy to deliver to the HTTP Client the data that is stored in the Client Proxy's cache.
- the actual response body is not transmitted from the Server Proxy to Client Proxy.
- Server Proxy stores the response data along with the associated URL and meta-data in its own data cache.
- Server Proxy on receiving the requested response data either from its own cache or from HTTP Server, computes the length and hash value for the newly received response data, and either newly computed length or hash value does not match with the corresponding length and hash value supplied by the Client Proxy, the cached copy of the response data, stored in Client Proxy's cache, is considered invalid.
- Server Proxy sends the newly received response data to the Client Proxy.
- Client Proxy then sends the response data to HTTP Client.
- Both Client Proxy and Server Proxy cache the new response data in their respective databases along with the associated URL and meta-data for their future use.
- MDBC method is possible based on placement of software functionality for HTTP Client, Client Proxy, Server Proxy and HTTP Server components described above. These alternate embodiments are briefly described here.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 13/186,157, filed Jul. 19, 2011, which is a continuation of U.S. patent application Ser. No. 11/017,931, filed on Dec. 22, 2004, which claims priority from U.S. Provisional Patent Application Ser. No. 60/531,615, filed on Dec. 23, 2003. U.S. patent application Ser. No. 11/017,931 issued to patent as U.S. Pat. No. 8,010,670. The entire contents of U.S. patent application Ser. No. 13/186,157, U.S. patent application Ser. No. 11/017,931 and U.S. Provisional Patent Application Ser. No. 60/531,615 are hereby incorporated by reference.
- The present invention relates to a method (named Meta-Data Based Caching, or MDBC) of caching data locally by a client while using HTTP protocol for downloading data from a server in order to reduce the volume of data communication and also possibly reduce the data transmission time.
- At present, large volumes of data are delivered over the Internet network to client computing devices such as desktop and laptop computers and various handheld digital devices using a communication protocol called, the Hyper Text Transfer Protocol (HTTP). The HTTP protocol can be visualized as a protocol for interaction between a HTTP client (or simply called client in this document) that sends requests for data, and a HTTP server (or simply called server in this document) that supplies the data. The client, after sending the request, waits for the server's response, and then normally, upon receipt of data, delivers the data to the end user. In many cases, the client is implemented by a software component called a web-browser. The server is usually implemented by a software component called a web-server. However, it is possible to use HTTP protocol by other types of software components to create a HTTP client or a HTTP server for exchange of data over the Internet. The client uses a text string called a Uniform Resource Locater (URL) to identify the data being requested by the client.
- Since it is often the case that the data corresponding to a specific URL remains constant for some period of time, the HTTP protocol provides a mechanism for making use of the data previously accessed from the server which may be cached locally by a client. Such methods are described in R. Fielding, J. Gettys, J. Mogul, H Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, “Request for Comments: 2616, Hypertext Transfer Protocol—HTTP/1.1,” Network Working Group, June 1999 (“Fielding”), which is hereby incorporated by reference herein.
- Generally, the primary benefits of caching data by the client are reduction in the volume of data transmitted by the server to the client, and reduction in the time required for accessing the data by the client. When a client locally stores or caches a copy of the data corresponding to a URL, the next time the same client requests the data for the same URL, the client's copy of the data corresponding to the URL is considered to be “fresh” or “stale” depending on whether the client's cached copy still contains the valid data or not. If the client's cache does contain a valid copy of the requested data, the client's copy is considered to be “fresh”. On the other hand, if the client's cached copy no longer contains valid data corresponding to the URL, the client's copy is considered to be “stale. The HTTP protocol outlined in Fielding essentially relies on one of two metrics to determine if the copy of the content cached at the client is “stale” or “fresh”:
-
- A. The protocol can rely on the server that supplies data (called origin-server) to explicitly provide the expiration time and/or date for the data.
- B. The client uses heuristics based on metrics specified by the HTTP protocol (such as the Last-Modified time) to estimate a plausible expiration time/date.
- In Method A, the origin-server provides an explicit expiration time/date for the data corresponding to the URL. The client's caching mechanism maintains a database that maps each named data to its respective expiration time/date. Thus, each time the data is requested, the client's caching mechanism checks the database to see if the data is in the local cache of the client and if the expiration time/date has passed. If the expiration time/date has not passed then the request is fulfilled directly from the local cache and the origin server is not consulted. This technique or method is known as the “expiration” method of cache control.
- Method B differs from Method A in that the origin-server does not explicitly specify an expiration time/date for each object, rather the caching mechanism associated with the client uses its own internal metrics to approximate an expiration date and time.
- Method A is the preferred caching method, and also the more accurate of the two, but it is generally only effective as long as the server's expiration times are carefully chosen. Unfortunately, for a large and complex server with dynamic data, it is almost impossible to know a priori how much time will pass before a specific data will semantically change.
- While Method B does not impose any requirements on server's administrators, it is not possible for this method to be perfectly accurate and, as a result, it may compromise semantic transparency.
- In general, caching, as described in Fielding has two specific methods for reducing the volume of data transmission during the interaction between a client and a server:
-
- I. Eliminate the need to send full requests, using an “expiration” mechanism (“Expiration Time Method”).
- II. Eliminate the need to send full responses, using a “validation” mechanism based on last-modified time (“Last-Modified Time Method”).
- As described earlier, Method I relies on the origin-server to supply an explicit expiration time/date for the data. According to this method, if the requested data is found in the local cache of the client, and it has not expired, the client need not send the request to the server.
- On the other hand, for using the Method II, the origin-server need not provide an expiration date for the data. With Method II, the client's caching mechanism checks its database for a cached version of the requested data. If a cached version is found, then a request is sent to the origin-server to send the data if and only if the requested content has been modified since the time the client cached the data. If the content has not been modified, then the server only sends a response header and thereby instructs the client to use the cached copy. However, if the data has been modified since the last access, the server sends the new data.
- Neither of Method I or Method II deals with a situation in which the data has been specified as not being suitable for caching by the server (or administrator thereof). In some situations, it may be simpler or more beneficial for a server to identify all data as not being suitable for caching so that there is no need to calculate/estimate an expiration time/date or other reason. As such, there is a need for a way to allow caching of many types of data, including that which is ordinarily indicated as “no cache”.
- The system and method of the invention builds upon and is intended to improve upon the existing methods described above by providing additional methods for ascertaining the validity of cached data between a client and server, and thus reduce the volume of data transmission requirements. The method is based on utilizing computed characteristics, called meta-data, associated with the response data for a particular URL.
- According to one embodiment of the invention, there is provided a system for caching data using a client-server model. The system includes: a) a client proxy and a server proxy in communication with each other and with the client and the server, respectively; b) a plurality of processors for calculating client proxy meta-data and server proxy meta-data related to the data cached by the client proxy and server proxy, respectively; and, c) a communication link for communicating said meta-data between the client proxy and the server proxy. At least one processor from the plurality of processors is further configured to compare the client proxy meta-data and the server proxy meta-data to determine a cache hit or miss.
- According to another embodiment of the invention, there is provided a method for optimizing the transmission of data from a server to a client said method comprising the steps of: a) upon a client request for data to a client proxy, determining if a prior version of said data exists in a client proxy cache, if so forwarding a request containing client proxy meta-data describing said prior version of said data to a server proxy; b) if at step a) said prior version of said data does not exist in said client proxy cache, sending a request for said data to said server proxy; c) upon receipt of a request from step a) said server proxy determining if said prior version of said data is current based on comparing said client proxy meta-data with server proxy meta-data describing the data requested, if said prior version of said data is current, informing said client proxy of this, if not then fetching the current data from the said server, returning current data and updating server proxy meta-data; d) upon receipt of a request from step b) fetching current data from said server, updating server proxy meta-data, and sending said current data to said client proxy; e) updating said client proxy meta-data when said client proxy receives current data from said server proxy; and f) forwarding said prior version of said data or said current data from said client proxy to said client.
- According to yet another embodiment of the invention, there is provided a method for ascertaining the validity of cached data on a HTTP client for a given URL using meta-data derived from response data previously fetched from the HTTP server for the same URL.
-
FIG. 1 shows the general structure of a meta-data based system for local cache utilization according to an embodiment of the invention. -
FIG. 2 shows a flowchart of the operation of a meta-data based method for local cache utilization according to an embodiment of the invention. - The software architecture for the MDBC method of interaction between a HTTP client and HTTP server is shown in
FIG. 1 . - In
FIG. 1 , the client computer is connected to the Internet using any type of link low or high bandwidth). HTTP Client inFIG. 1 represents any HTTP client that requests data from a server using the HTTP protocol. HTTP Server component inFIG. 1 represents any HTTP server that supplies data to requesting clients. HTTP Client on the client computer does not directly interact with HTTP Server. Rather, two intermediate software components are used—one on the client side, and the other on the server side. The client side component is called Client Proxy. The server side component is called Server Proxy. A Server Proxy can concurrently interact with (or serve) more than one Client Proxy components located on different client computers. Instead of sending its HTTP request for data directly to HTTP Server, HTTP Client sends the data to Client Proxy. Client Proxy, as described later, may modify the original request from HTTP Client and then sends the request to Server Proxy. Depending upon the situation, as described later, Server Proxy first attempts to respond to Client Proxy's request using its own cached data, failing which it may send the request to HTTP Server. Similarly, an HTTP response from HTTP Server is communicated through the Server Proxy and then to Client Proxy, before being delivered to HTTP Client. Optionally, all the data that is communicated between Client Proxy and Server Proxy can be optimized using a customized protocol between Client Proxy and Server Proxy by using optimization techniques, including but not limited to, data compression techniques. - Based on the software architecture shown in
FIG. 1 , the caching techniques outlined in Fielding are improved using the algorithm described as follows: - Prior to sending a HTTP request for data, HTTP Client may optionally search its own cache and then determine if a valid copy of the required data is present in its own cache or whether a HTTP request for a given URL needs to be sent.
- Next, for each data being requested, HTTP Client sends Client Proxy a request of the following form:
- GET <URL> PROTOCOL VERSION
- For instance:
- GET http://www.w3.org/ HTTP/1.1
- Both Client Proxy and Server Proxy maintain their respective databases that hold, for a certain period of time, additional information about each HTTP response data corresponding to a URL that has previously been received along with the actual response data. This additional information is called meta-data associated with the response data. This meta-data includes, but is not limited to, the URL associated with the response data, (more generally, the meta-data can be indexed or keyed to the requested URL) the type of data in the response data (for example, a text file, or a GIF image file), the length of the response data, a hash value associated with the response data. The hash value could be computed using CRC-16, CRC-32, SHA1, MD2, MD4, MD5, or any other suitable algorithm. By design, Client Proxy and Server Proxy are coordinated with respect to the meta-data elements used in a particular implementation of MDBC method and algorithms used for computing each such meta-data element.
- In a case in which no prior response data is found in Client Proxy cache for the given URL, the Client Proxy simply forwards HTTP Client's request to Server Proxy. Server Proxy first searches its own data cache for the response data for the URL specified by the Client Proxy that is currently valid based on either Expiration Time Method or the Last-Modified Time Method. If such data is found, Server Proxy returns the response data to the Client Proxy. Otherwise, Server Proxy interacts as a regular HTTP client with HTTP Server as described in Fielding and receives the response data from the HTTP Server. Server Proxy sends the response data to Client Proxy. In either case, the Client Proxy, in turn, sends the response data to HTTP Client. Both Client Proxy and Server Proxy cache the response data along with the meta-data in their respective databases for their future use.
- In a case in which, a prior response corresponding to the requested URL is found in Client Proxy's cache, Client Proxy, as part of a modified request, forwards to Server Proxy elements of the meta-data associated with the prior response data for that specific URL.
- Server Proxy, upon receiving the request from the Client Proxy, first attempts to fulfill the request from the Client Proxy by examining its own cache. If a prior response data for the particular URL is found in Server Proxy's cache, which is still valid based on either the Expiration Time Method or the Last-Modified Time Method, then Server Proxy retrieves the meta-data for the response data from its cache and compares each element of the newly computed meta-data with the corresponding values of meta-data supplied by Client Proxy. If the values for all the corresponding elements of meta-data match, then the Server Proxy informs the Client Proxy to deliver to HTTP Client the response data that is stored in the Client Proxy's cache. The actual response body is not transmitted from the Server Proxy to Client Proxy. Client Proxy delivers the HTTP response data from the Client Proxy's cache to the HTTP client.
- If, on the other hand, Server Proxy does not find a valid prior response data for the particular URL in its cache then Server Proxy acts as a HTTP client to the HTTP Server and sends a regular HTTP request based on the protocol described in Fielding to HTTP Server. HTTP Server sends the HTTP response data to Server Proxy. On receiving response data from HTTP Server, Server Proxy computes the meta-data for the newly received response data from HTTP Server, using the same algorithm as was used by the Client Proxy, and compares each element of the newly computed meta-data with the corresponding values of meta-data supplied by Client Proxy. If the values for all the corresponding elements of meta-data match, then the Server Proxy informs the Client Proxy to deliver to the HTTP Client the data that is stored in the Client Proxy's cache. The actual response body is not transmitted from the Server Proxy to Client Proxy. Server Proxy stores the response data along with the associated URL and meta-data in its own cache.
- Finally, if Server Proxy, on receiving the requested response data either from its own cache or from HTTP Server, computes the meta-data for the newly received response data, and any element of the newly computed meta-data does not match with the corresponding element of the meta-data supplied by the Client Proxy, the cached copy of the response data, stored in Client Proxy's cache, is considered invalid. In this case, Server Proxy sends the newly received response data to the Client Proxy. Client Proxy then sends the response data to HTTP Client. Both Client Proxy and Server Proxy cache the new response data in their respective databases along with the associated URL and meta-data for their future use.
- This method may result in a significant reduction in the volume of data transmission from Server Proxy to Client Proxy, and therefore, it may also reduce the time elapsed from the time the request was generated by the HTTP Client and the time the response is delivered to the HTTP Client. It is particularly beneficial when Client Proxy and Server Proxy are connected over a low bandwidth link.
- The caching method according to embodiments of the invention coexists with those techniques described in Fielding, but also handles cases the techniques in Fielding may miss. For instance, even data marked as “Cache-Control: private” or “Cache Control: no-cache” (indicating that the data should not be cached) can be safely cached using the MDBC method according to embodiments of the invention. Also, the meta-data can be used to supplement the methods in Fielding as additional or independent metrics for ascertaining whether a cached copy of response data is valid or not.
- Furthermore, so long as a suitable meta-data is used, the HTTP Client can achieve a high degree of certainty in receiving the requested data that is correct, and not “stale”.
- As an example, a situation is illustrated here where Client Proxy uses the length of the response data and a computed hash value as two elements of the meta-data (in addition to the URL string itself) associated with a response data for a URL. For each data being requested, HTTP Client sends Client Proxy a request of the following form:
- GET <URL> PROTOCOL VERSION
- For instance:
- GET http://www.w3.org/ HTTP/1.1
- In a case in which no prior response data is found in Client Proxy cache for the given URL, the Client Proxy simply forwards HTTP Client's request to Server Proxy. Server Proxy first searches its own data cache for the response data for the URL specified by the Client Proxy that is currently valid based on either the Expiration Time Method or Last-Modified Time Method. If such data is found, Proxy Server returns the response data to the Client Proxy. Otherwise, Server Proxy interacts as a regular HTTP client with HTTP Server as described in Fielding and receives the response data from the HTTP Server. Server Proxy sends the response data to Client Proxy. In either case, Client Proxy, in turn, sends the response data to HTTP Client. Both Client Proxy and Server Proxy cache the response data, along with the URL string, length and hash value, in their respective databases for their future use.
- In the case where a prior response corresponding to the requested URL is found in Client Proxy's cache, Client Proxy, as part of a modified request, forwards to Server Proxy the request for the URL along with the length and the hash value of the last response data it received for that specific URL.
- Server Proxy, upon receiving the request from the Client Proxy, first attempts to fulfill the request from the Client Proxy by examining its own cache. If a prior response data for the particular URL is found in Server Proxy's cache, which is still valid based on either Expiration Time Method or Last-Modified Time Method, then Server Proxy computes the length and hash value for the response data from its cache, using the same algorithm as was used by the Client Proxy, and compares new length and hash value with the length and hash value respectively supplied by Client Proxy. If the length and hash values both match, Server Proxy informs Client Proxy to deliver HTTP Client the response data that is stored in Client Proxy's cache. The actual body of response data is not transmitted from the Server Proxy to Client Proxy. Client Proxy delivers the HTTP response data from the Client Proxy's cache to the HTTP Client.
- If, on the other hand, Server Proxy does not find a valid prior response data for the particular URL in its cache then Server Proxy acts as a HTTP client to the HTTP Server and sends a regular HTTP request based on the protocol described in Fielding to HTTP Server. HTTP Server sends the HTTP response data to Server Proxy. On receiving response data from the HTTP Server, Server Proxy computes the length and hash value for the newly received response data from HTTP Server, using the same algorithm as was used by Client Proxy, and compares the newly computed length and hash value with the values of length and hash value respectively, supplied by Client Proxy. If the length and hash value match with the length and hash value supplied by the Client Proxy, then the Server Proxy informs the Client Proxy to deliver to the HTTP Client the data that is stored in the Client Proxy's cache. The actual response body is not transmitted from the Server Proxy to Client Proxy. Server Proxy stores the response data along with the associated URL and meta-data in its own data cache.
- Finally, if Server Proxy, on receiving the requested response data either from its own cache or from HTTP Server, computes the length and hash value for the newly received response data, and either newly computed length or hash value does not match with the corresponding length and hash value supplied by the Client Proxy, the cached copy of the response data, stored in Client Proxy's cache, is considered invalid. In this case, Server Proxy sends the newly received response data to the Client Proxy. Client Proxy then sends the response data to HTTP Client. Both Client Proxy and Server Proxy cache the new response data in their respective databases along with the associated URL and meta-data for their future use.
- Other embodiments of the MDBC method are possible based on placement of software functionality for HTTP Client, Client Proxy, Server Proxy and HTTP Server components described above. These alternate embodiments are briefly described here.
-
- 1. HTTP Client and the Client Proxy can be located on different computers. A single Client Proxy, in this case, can serve one or more HTTP Clients located on different computers.
- 2. The functionality of the HTTP Client and Client Proxy can be combined in a single software component. For example, a web-browser can implement the combined functionality of HTTP Client and Client Proxy.
- 3. Server Proxy and HTTP Server may be located on the same computer.
- 4. The functionality of Server Proxy and Server can be combined into a single software component.
- 5. The MDBC method is also applicable and can be extended to other name/value-based protocols such as the file transfer protocol (FTP).
- It should be recognized that the embodiments described herein and shown in the drawing figures are meant to be illustrative only and should not be taken as limiting the scope of invention. Those skilled in the art will recognize that the elements of the illustrated embodiments can be modified in arrangement and detail without departing from the spirit of the invention. Therefore, the invention as described herein contemplates all such embodiments and modified embodiments as may come within the scope of the following claims or equivalents thereof.
Claims (17)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/615,748 US20130013673A1 (en) | 2003-12-23 | 2012-09-14 | Meta-data based method for local cache utilization |
US14/686,101 US9967359B2 (en) | 2003-12-23 | 2015-04-14 | Meta-data based method for local cache utilization |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US53161503P | 2003-12-23 | 2003-12-23 | |
US11/017,931 US8010670B2 (en) | 2003-12-23 | 2004-12-22 | Meta-data based method for local cache utilization |
US13/186,157 US8291081B2 (en) | 2003-12-23 | 2011-07-19 | Meta-data based method for local cache utilization |
US13/615,748 US20130013673A1 (en) | 2003-12-23 | 2012-09-14 | Meta-data based method for local cache utilization |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/186,157 Continuation US8291081B2 (en) | 2003-12-23 | 2011-07-19 | Meta-data based method for local cache utilization |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/686,101 Continuation US9967359B2 (en) | 2003-12-23 | 2015-04-14 | Meta-data based method for local cache utilization |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130013673A1 true US20130013673A1 (en) | 2013-01-10 |
Family
ID=34680998
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/017,931 Active 2028-07-11 US8010670B2 (en) | 2003-12-23 | 2004-12-22 | Meta-data based method for local cache utilization |
US13/186,157 Expired - Lifetime US8291081B2 (en) | 2003-12-23 | 2011-07-19 | Meta-data based method for local cache utilization |
US13/615,748 Abandoned US20130013673A1 (en) | 2003-12-23 | 2012-09-14 | Meta-data based method for local cache utilization |
US14/686,101 Expired - Lifetime US9967359B2 (en) | 2003-12-23 | 2015-04-14 | Meta-data based method for local cache utilization |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/017,931 Active 2028-07-11 US8010670B2 (en) | 2003-12-23 | 2004-12-22 | Meta-data based method for local cache utilization |
US13/186,157 Expired - Lifetime US8291081B2 (en) | 2003-12-23 | 2011-07-19 | Meta-data based method for local cache utilization |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/686,101 Expired - Lifetime US9967359B2 (en) | 2003-12-23 | 2015-04-14 | Meta-data based method for local cache utilization |
Country Status (1)
Country | Link |
---|---|
US (4) | US8010670B2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140108590A1 (en) * | 2012-10-11 | 2014-04-17 | Simon Hunt | Efficient shared image deployment |
US20140337415A1 (en) * | 2013-01-25 | 2014-11-13 | Canon Kabushiki Kaisha | Communication apparatus, method for controlling the same, and program |
US20150271739A1 (en) * | 2014-03-20 | 2015-09-24 | Canon Kabushiki Kaisha | Relay apparatus, communication apparatus, control methods thereof, system, and non-transitory computer-readable storage medium |
US20150271678A1 (en) * | 2014-03-20 | 2015-09-24 | Canon Kabushiki Kaisha | Relay apparatus, relay method, relay system, and non-transitory computer-readable storage medium |
US20150295987A1 (en) * | 2012-10-26 | 2015-10-15 | Eutelsat S A | Method for the recovery of content corresponding to a url address by a client device |
US9639629B1 (en) * | 2011-08-31 | 2017-05-02 | Instart Logic, Inc. | Accelerating the downloading of content to an application |
Families Citing this family (127)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003058483A1 (en) | 2002-01-08 | 2003-07-17 | Seven Networks, Inc. | Connection architecture for a mobile network |
US7853563B2 (en) | 2005-08-01 | 2010-12-14 | Seven Networks, Inc. | Universal data aggregation |
US7917468B2 (en) | 2005-08-01 | 2011-03-29 | Seven Networks, Inc. | Linking of personal information management data |
US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
US7949726B2 (en) * | 2004-03-12 | 2011-05-24 | Ocean And Coastal Environmental Sensing, Inc. | System and method for delivering information on demand |
US8234414B2 (en) * | 2004-03-31 | 2012-07-31 | Qurio Holdings, Inc. | Proxy caching in a photosharing peer-to-peer network to improve guest image viewing performance |
US7788713B2 (en) * | 2004-06-23 | 2010-08-31 | Intel Corporation | Method, apparatus and system for virtualized peer-to-peer proxy services |
US8676922B1 (en) | 2004-06-30 | 2014-03-18 | Google Inc. | Automatic proxy setting modification |
WO2006045102A2 (en) | 2004-10-20 | 2006-04-27 | Seven Networks, Inc. | Method and apparatus for intercepting events in a communication system |
US7698386B2 (en) * | 2004-11-16 | 2010-04-13 | Qurio Holdings, Inc. | Serving content from an off-line peer server in a photosharing peer-to-peer network in response to a guest request |
US7706781B2 (en) | 2004-11-22 | 2010-04-27 | Seven Networks International Oy | Data security in a mobile e-mail service |
FI117152B (en) | 2004-12-03 | 2006-06-30 | Seven Networks Internat Oy | E-mail service provisioning method for mobile terminal, involves using domain part and further parameters to generate new parameter set in list of setting parameter sets, if provisioning of e-mail service is successful |
US7752633B1 (en) | 2005-03-14 | 2010-07-06 | Seven Networks, Inc. | Cross-platform event engine |
US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
WO2006136660A1 (en) | 2005-06-21 | 2006-12-28 | Seven Networks International Oy | Maintaining an ip connection in a mobile network |
JP4852906B2 (en) * | 2005-06-24 | 2012-01-11 | 富士ゼロックス株式会社 | Cooperation processing system and apparatus |
CA2513018A1 (en) * | 2005-07-22 | 2007-01-22 | Research In Motion Limited | Method for training a proxy server for content delivery based on communication of state information from a mobile device browser |
CA2513022A1 (en) * | 2005-07-22 | 2007-01-22 | Research In Motion Limited | System and method for communicating state management between a browser user-agent and a mobile data server |
CA2513016A1 (en) * | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A secure method of synchronizing cache contents of a mobile browser with a proxy server |
CA2513019A1 (en) * | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A method for communicating state information between a server and a mobile device browser with version handling |
CA2513014A1 (en) * | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A method of controlling delivery of multi-part content from an origin server to a mobile device browser via a proxy server |
US8688801B2 (en) | 2005-07-25 | 2014-04-01 | Qurio Holdings, Inc. | Syndication feeds for peer computer devices and peer networks |
US20070091907A1 (en) * | 2005-10-03 | 2007-04-26 | Varad Seshadri | Secured media communication across enterprise gateway |
US8005889B1 (en) | 2005-11-16 | 2011-08-23 | Qurio Holdings, Inc. | Systems, methods, and computer program products for synchronizing files in a photosharing peer-to-peer network |
US8788572B1 (en) | 2005-12-27 | 2014-07-22 | Qurio Holdings, Inc. | Caching proxy server for a peer-to-peer photosharing system |
US7769395B2 (en) | 2006-06-20 | 2010-08-03 | Seven Networks, Inc. | Location-based operations and messaging |
US8004973B2 (en) * | 2006-04-25 | 2011-08-23 | Citrix Systems, Inc. | Virtual inline configuration for a network device |
US20080317241A1 (en) * | 2006-06-14 | 2008-12-25 | Derek Wang | Code-based echo cancellation |
US20090016333A1 (en) * | 2006-06-14 | 2009-01-15 | Derek Wang | Content-based adaptive jitter handling |
US7480500B1 (en) * | 2006-06-14 | 2009-01-20 | Divitas Networks, Inc. | Divitas protocol proxy and methods therefor |
EP2033408A2 (en) * | 2006-06-14 | 2009-03-11 | Divitas Networks, Inc. | Divitas protocol proxy and methods therefor |
US7565159B2 (en) * | 2006-06-14 | 2009-07-21 | Divitas Networks, Inc. | Methods and arrangement for implementing an active call handover by employing a switching component |
US20080140767A1 (en) * | 2006-06-14 | 2008-06-12 | Prasad Rao | Divitas description protocol and methods therefor |
DE102006033301A1 (en) | 2006-07-17 | 2008-01-31 | Vodafone Holding Gmbh | Methods and apparatus for caching data in a cellular network |
US7949747B1 (en) * | 2006-08-18 | 2011-05-24 | Ecowater Systems Llc | Method and system of communication in a wireless water treatment system |
US8260713B2 (en) * | 2006-08-23 | 2012-09-04 | Royaltyshare, Inc. | Web-based system providing royalty processing and reporting services |
US20080155016A1 (en) * | 2006-12-22 | 2008-06-26 | Tsai Wei K | Content procurement architecture |
US20080162486A1 (en) * | 2006-12-27 | 2008-07-03 | Research In Motion Limited | Method and apparatus for storing data from a network address |
US10156953B2 (en) * | 2006-12-27 | 2018-12-18 | Blackberry Limited | Method for presenting data on a small screen |
US8099386B2 (en) * | 2006-12-27 | 2012-01-17 | Research In Motion Limited | Method and apparatus for synchronizing databases connected by wireless interface |
US8275741B2 (en) * | 2006-12-27 | 2012-09-25 | Research In Motion Limited | Method and apparatus for memory management in an electronic device |
US8812651B1 (en) * | 2007-02-15 | 2014-08-19 | Google Inc. | Systems and methods for client cache awareness |
US8296385B2 (en) * | 2007-04-23 | 2012-10-23 | Lenovo (Singapore) Pte. Ltd. | Apparatus and method for selective engagement in software distribution |
US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
US8712825B1 (en) | 2007-07-03 | 2014-04-29 | Royaltyshare, Inc. | Web-based royalty system and user interface |
US20090119375A1 (en) * | 2007-11-05 | 2009-05-07 | Research In Motion Limited | Method and system for optimizing delivery of mobile content using differential metadata updates |
EP2056560A1 (en) | 2007-11-05 | 2009-05-06 | Research In Motion Limited | Method and system for optimizing delivery of mobile content using differential metadata updates |
US8364181B2 (en) | 2007-12-10 | 2013-01-29 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
US20090193338A1 (en) | 2008-01-28 | 2009-07-30 | Trevor Fiatal | Reducing network and battery consumption during content delivery and playback |
US20090215438A1 (en) * | 2008-02-23 | 2009-08-27 | Ajay Mittal | Methods for performing transparent callback |
US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
US8078158B2 (en) | 2008-06-26 | 2011-12-13 | Seven Networks, Inc. | Provisioning applications for a mobile device |
US20100030607A1 (en) * | 2008-08-02 | 2010-02-04 | Royaltyshare, Inc. | Digital Content Management System with Methodologies for Lifecycle Management of Digital Content |
EP2164231A1 (en) * | 2008-09-15 | 2010-03-17 | Jentro Technologies GmbH | Mobile phone optimized online communication |
US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
US20100222053A1 (en) * | 2009-02-27 | 2010-09-02 | Girisrinivasarao Athulurutirumala | Arrangement and methods for establishing a telecommunication connection based on a heuristic model |
US8463846B2 (en) * | 2010-05-06 | 2013-06-11 | Cdnetworks Co., Ltd. | File bundling for cache servers of content delivery networks |
WO2012018430A1 (en) | 2010-07-26 | 2012-02-09 | Seven Networks, Inc. | Mobile network traffic coordination across multiple applications |
US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
GB2495877B (en) | 2010-07-26 | 2013-10-02 | Seven Networks Inc | Distributed implementation of dynamic wireless traffic policy |
WO2012018556A2 (en) | 2010-07-26 | 2012-02-09 | Ari Backholm | Mobile application traffic optimization |
WO2012060995A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
US9330196B2 (en) | 2010-11-01 | 2016-05-03 | Seven Networks, Llc | Wireless traffic management system cache optimization using http headers |
US8326985B2 (en) | 2010-11-01 | 2012-12-04 | Seven Networks, Inc. | Distributed management of keep-alive message signaling for mobile network resource conservation and optimization |
EP2635973A4 (en) | 2010-11-01 | 2014-01-15 | Seven Networks Inc | Caching adapted for mobile application behavior and network conditions |
US9060032B2 (en) | 2010-11-01 | 2015-06-16 | Seven Networks, Inc. | Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic |
US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
WO2012060997A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Application and network-based long poll request detection and cacheability assessment therefor |
CA2798523C (en) | 2010-11-22 | 2015-02-24 | Seven Networks, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
WO2012071384A2 (en) | 2010-11-22 | 2012-05-31 | Michael Luna | Optimization of resource polling intervals to satisfy mobile device requests |
WO2012094675A2 (en) | 2011-01-07 | 2012-07-12 | Seven Networks, Inc. | System and method for reduction of mobile network traffic used for domain name system (dns) queries |
GB2503405B (en) | 2011-04-19 | 2015-06-24 | Seven Networks Inc | Device resource sharing for network resource conservation |
GB2504037B (en) * | 2011-04-27 | 2014-12-24 | Seven Networks Inc | Mobile device which offloads requests made by a mobile application to a remote entity for conservation of mobile device and network resources |
WO2012149434A2 (en) | 2011-04-27 | 2012-11-01 | Seven Networks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
EP2737742A4 (en) | 2011-07-27 | 2015-01-28 | Seven Networks Inc | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
US8977755B2 (en) | 2011-12-06 | 2015-03-10 | Seven Networks, Inc. | Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation |
US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
WO2013086447A1 (en) | 2011-12-07 | 2013-06-13 | Seven Networks, Inc. | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
EP2788889A4 (en) * | 2011-12-07 | 2015-08-12 | Seven Networks Inc | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
US8861354B2 (en) | 2011-12-14 | 2014-10-14 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
EP2792188B1 (en) | 2011-12-14 | 2019-03-20 | Seven Networks, LLC | Mobile network reporting and usage analytics system and method using aggregation of data in a distributed traffic optimization system |
US9832095B2 (en) | 2011-12-14 | 2017-11-28 | Seven Networks, Llc | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
GB2499306B (en) | 2012-01-05 | 2014-10-22 | Seven Networks Inc | Managing user interaction with an application on a mobile device |
US20130198258A1 (en) * | 2012-01-28 | 2013-08-01 | International Business Machines Corporation | Database improvement system |
US9203864B2 (en) | 2012-02-02 | 2015-12-01 | Seven Networks, Llc | Dynamic categorization of applications for network access in a mobile network |
US9326189B2 (en) | 2012-02-03 | 2016-04-26 | Seven Networks, Llc | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
DE102012203463B4 (en) * | 2012-03-05 | 2013-04-18 | Hochschule Ruhr West | Method for providing web services of a mobile web service provider |
CN103313303A (en) * | 2012-03-08 | 2013-09-18 | 株式会社Ntt都科摩 | Wireless access point, wireless work station and work method of wireless access point and wireless work station |
US9215127B2 (en) * | 2012-03-12 | 2015-12-15 | Network Coding, Inc. | Non-intrusive proxy system and method for applications without proxy support |
US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
US20130268656A1 (en) | 2012-04-10 | 2013-10-10 | Seven Networks, Inc. | Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network |
US9088461B2 (en) * | 2012-06-21 | 2015-07-21 | International Business Machines Corporation | Common web accessible data store for client side page processing |
US9736260B2 (en) * | 2012-06-21 | 2017-08-15 | Cisco Technology, Inc. | Redirecting from a cloud service to a third party website to save costs without sacrificing security |
WO2014011216A1 (en) | 2012-07-13 | 2014-01-16 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
US9635121B2 (en) * | 2012-08-06 | 2017-04-25 | Paypal, Inc. | Systems and methods for caching HTTP post requests and responses |
US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
US9489188B1 (en) * | 2012-11-14 | 2016-11-08 | Amazon Technologies, Inc. | Tag-based deployment |
US9307493B2 (en) | 2012-12-20 | 2016-04-05 | Seven Networks, Llc | Systems and methods for application management of mobile device radio state promotion and demotion |
US9300748B2 (en) | 2013-01-16 | 2016-03-29 | Cisco Technology, Inc. | Method for optimizing WAN traffic with efficient indexing scheme |
US9306997B2 (en) * | 2013-01-16 | 2016-04-05 | Cisco Technology, Inc. | Method for optimizing WAN traffic with deduplicated storage |
US9509736B2 (en) | 2013-01-16 | 2016-11-29 | Cisco Technology, Inc. | Method for optimizing WAN traffic |
US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
US9398066B1 (en) * | 2013-03-06 | 2016-07-19 | Amazon Technologies, Inc. | Server defenses against use of tainted cache |
US9471533B1 (en) | 2013-03-06 | 2016-10-18 | Amazon Technologies, Inc. | Defenses against use of tainted cache |
US9326185B2 (en) | 2013-03-11 | 2016-04-26 | Seven Networks, Llc | Mobile network congestion recognition for optimization of mobile traffic |
US20140366002A1 (en) * | 2013-06-11 | 2014-12-11 | Sap Ag | Searching for an entity most suited to provide knowledge regarding an object |
KR20150003550A (en) * | 2013-07-01 | 2015-01-09 | 삼성전자주식회사 | Apparatus and Method for transmitting web contents |
US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
WO2015054832A1 (en) * | 2013-10-16 | 2015-04-23 | Empire Technology Development Llc | Two-level cloud system migration |
US9979644B2 (en) * | 2014-07-13 | 2018-05-22 | Cisco Technology, Inc. | Linking to content using information centric networking |
US10061852B1 (en) * | 2015-05-19 | 2018-08-28 | Amazon Technologies, Inc. | Transparent proxy tunnel caching for database access |
CA2954839A1 (en) * | 2016-01-22 | 2017-07-22 | Wal-Mart Stores, Inc. | Systems and methods of enabling forecasting |
US10402373B1 (en) * | 2016-02-08 | 2019-09-03 | Amazon Technologies, Inc. | Filesystem redirection |
US10237364B2 (en) * | 2016-03-24 | 2019-03-19 | International Business Machines Corporation | Resource usage anonymization |
US11349922B2 (en) | 2016-04-06 | 2022-05-31 | Marvell Asia Pte Ltd. | System and method for a database proxy |
US10237350B2 (en) * | 2016-04-06 | 2019-03-19 | Reniac, Inc. | System and method for a database proxy |
US10225237B2 (en) | 2016-10-17 | 2019-03-05 | Zscaler, Inc. | Systems and methods for improving HTTPS security |
US10387383B2 (en) | 2017-02-15 | 2019-08-20 | Google Llc | Systems and methods for providing access to a data file stored at a data storage system |
US11157242B2 (en) * | 2019-09-30 | 2021-10-26 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for local web components development within a cloud based computing environment |
US11429595B2 (en) | 2020-04-01 | 2022-08-30 | Marvell Asia Pte Ltd. | Persistence of write requests in a database proxy |
CN112671733A (en) * | 2020-12-16 | 2021-04-16 | 平安科技(深圳)有限公司 | Data communication method, key management system, device, and storage medium |
US12278876B1 (en) * | 2024-04-10 | 2025-04-15 | Uab 360 It | Augmenting web servers with endpoints |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5859971A (en) * | 1996-02-15 | 1999-01-12 | International Business Machines Corp. | Differencing client/server communication system for use with CGI forms |
US5867661A (en) * | 1996-02-15 | 1999-02-02 | International Business Machines Corporation | Method and apparatus of using virtual sockets for reducing data transmitted over a wireless communication link between a client web browser and a host web server using a standard TCP protocol |
US5878213A (en) * | 1996-02-15 | 1999-03-02 | International Business Machines Corporation | Methods, systems and computer program products for the synchronization of time coherent caching system |
US5931904A (en) * | 1996-10-11 | 1999-08-03 | At&T Corp. | Method for reducing the delay between the time a data page is requested and the time the data page is displayed |
US20020026563A1 (en) * | 1999-01-25 | 2002-02-28 | John T. Chamberlain | Cache override control in an apparatus for caching dynamic content |
US20020194382A1 (en) * | 2001-06-04 | 2002-12-19 | Kausik Balas Natarajan | Method and system for efficient and automated version management of embedded objects in web documents |
US20030236857A1 (en) * | 2002-03-07 | 2003-12-25 | International Business Machines Corporation | Network service system and program using data processing |
US20050065999A1 (en) * | 1998-09-01 | 2005-03-24 | Swarup Acharya | Computer implemented method and apparatus for fulfilling a request for information content with a user-selectable version of a file containing that information content |
US7200756B2 (en) * | 2002-06-25 | 2007-04-03 | Microsoft Corporation | Base cryptographic service provider (CSP) methods and apparatuses |
US7376790B2 (en) * | 2001-06-12 | 2008-05-20 | Network Appliance, Inc. | Caching media data using content sensitive object identifiers |
US20120271905A1 (en) * | 2004-03-31 | 2012-10-25 | Qurio Holdings, Inc. | Proxy caching in a photosharing peer-to-peer network to improve guest image viewing performance |
US20130110906A1 (en) * | 2011-11-02 | 2013-05-02 | Microsoft Corporation | Browser cache assist for accessing web-based content |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6038601A (en) * | 1997-07-21 | 2000-03-14 | Tibco, Inc. | Method and apparatus for storing and delivering documents on the internet |
US6085193A (en) * | 1997-09-29 | 2000-07-04 | International Business Machines Corporation | Method and system for dynamically prefetching information via a server hierarchy |
US6389460B1 (en) * | 1998-05-13 | 2002-05-14 | Compaq Computer Corporation | Method and apparatus for efficient storage and retrieval of objects in and from an object storage device |
US6330561B1 (en) * | 1998-06-26 | 2001-12-11 | At&T Corp. | Method and apparatus for improving end to end performance of a data network |
US6178461B1 (en) * | 1998-12-08 | 2001-01-23 | Lucent Technologies Inc. | Cache-based compaction technique for internet browsing using similar objects in client cache as reference objects |
US20060224752A1 (en) * | 1999-05-03 | 2006-10-05 | Parekh Sanjay M | Determining geographic locations of private network Internet users |
US6505230B1 (en) * | 1999-05-14 | 2003-01-07 | Pivia, Inc. | Client-server independent intermediary mechanism |
US7305473B2 (en) * | 1999-05-28 | 2007-12-04 | The Coca-Cola Company | Provision of transparent proxy services to a user of a client device |
US6553409B1 (en) * | 1999-07-09 | 2003-04-22 | Microsoft Corporation | Background cache synchronization |
US6510458B1 (en) * | 1999-07-15 | 2003-01-21 | International Business Machines Corporation | Blocking saves to web browser cache based on content rating |
US6658462B1 (en) * | 1999-08-26 | 2003-12-02 | International Business Machines Corporation | System, method, and program for balancing cache space requirements with retrieval access time for large documents on the internet |
US7577754B2 (en) * | 2000-04-28 | 2009-08-18 | Adara Networks, Inc. | System and method for controlling access to content carried in a caching architecture |
US6826626B1 (en) * | 2000-07-21 | 2004-11-30 | Clear Blue Technologies Management, Inc. | Method of and apparatus for rapid retrieval of data in a content distribution network |
US6704024B2 (en) * | 2000-08-07 | 2004-03-09 | Zframe, Inc. | Visual content browsing using rasterized representations |
US6795848B1 (en) * | 2000-11-08 | 2004-09-21 | Hughes Electronics Corporation | System and method of reading ahead of objects for delivery to an HTTP proxy server |
US7035911B2 (en) * | 2001-01-12 | 2006-04-25 | Epicrealm, Licensing Llc | Method and system for community data caching |
US7188145B2 (en) * | 2001-01-12 | 2007-03-06 | Epicrealm Licensing Llc | Method and system for dynamic distributed data caching |
US7269784B1 (en) * | 2001-01-22 | 2007-09-11 | Kasriel Stephane | Server-originated differential caching |
US7383348B2 (en) * | 2001-06-13 | 2008-06-03 | Kabushiki Kaisha Toshiba | Data transfer scheme using caching technique for reducing network load |
US7185063B1 (en) * | 2001-06-22 | 2007-02-27 | Digital River, Inc. | Content delivery network using differential caching |
JP4274710B2 (en) * | 2001-06-28 | 2009-06-10 | 株式会社日立製作所 | Communication relay device |
US7024452B1 (en) * | 2001-07-13 | 2006-04-04 | Vignette Corporation | Method and system for file-system based caching |
EP1563389A4 (en) * | 2001-08-01 | 2008-06-25 | Actona Technologies Ltd | Virtual file-sharing network |
US6883068B2 (en) * | 2001-12-17 | 2005-04-19 | Sun Microsystems, Inc. | Methods and apparatus for implementing a chche replacement scheme |
US7412535B2 (en) * | 2001-12-19 | 2008-08-12 | International Business Machines Corporation | Method and system for caching fragments while avoiding parsing of pages that do not contain fragments |
US7509393B2 (en) * | 2001-12-19 | 2009-03-24 | International Business Machines Corporation | Method and system for caching role-specific fragments |
US6907501B2 (en) * | 2002-01-25 | 2005-06-14 | Ntt Docomo Inc. | System for management of cacheable streaming content in a packet based communication network with mobile hosts |
US7296051B1 (en) * | 2002-02-19 | 2007-11-13 | Digital River, Inc. | Predictive predownload of templates with delta encoding |
US7487261B1 (en) * | 2002-02-22 | 2009-02-03 | Digital River, Inc. | Delta caching service |
JP4020676B2 (en) * | 2002-03-26 | 2007-12-12 | 株式会社東芝 | Web system and Web system control method |
EP1522191B1 (en) * | 2002-04-19 | 2013-07-17 | Opentv, Inc. | Supporting common interactive television functionality through presentation engine syntax |
US7725557B2 (en) * | 2002-06-24 | 2010-05-25 | Microsoft Corporation | Client-side caching of streaming media content |
US20040003101A1 (en) * | 2002-06-26 | 2004-01-01 | Roth David J. | Caching control for streaming media |
US7953820B2 (en) * | 2002-09-11 | 2011-05-31 | Hughes Network Systems, Llc | Method and system for providing enhanced performance of web browsing |
US7171469B2 (en) * | 2002-09-16 | 2007-01-30 | Network Appliance, Inc. | Apparatus and method for storing data in a proxy cache in a network |
US7120666B2 (en) * | 2002-10-30 | 2006-10-10 | Riverbed Technology, Inc. | Transaction accelerator for client-server communication systems |
US7349929B2 (en) * | 2003-04-25 | 2008-03-25 | Sap Ag | Accessing data based on user identity |
-
2004
- 2004-12-22 US US11/017,931 patent/US8010670B2/en active Active
-
2011
- 2011-07-19 US US13/186,157 patent/US8291081B2/en not_active Expired - Lifetime
-
2012
- 2012-09-14 US US13/615,748 patent/US20130013673A1/en not_active Abandoned
-
2015
- 2015-04-14 US US14/686,101 patent/US9967359B2/en not_active Expired - Lifetime
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5859971A (en) * | 1996-02-15 | 1999-01-12 | International Business Machines Corp. | Differencing client/server communication system for use with CGI forms |
US5867661A (en) * | 1996-02-15 | 1999-02-02 | International Business Machines Corporation | Method and apparatus of using virtual sockets for reducing data transmitted over a wireless communication link between a client web browser and a host web server using a standard TCP protocol |
US5878213A (en) * | 1996-02-15 | 1999-03-02 | International Business Machines Corporation | Methods, systems and computer program products for the synchronization of time coherent caching system |
US5931904A (en) * | 1996-10-11 | 1999-08-03 | At&T Corp. | Method for reducing the delay between the time a data page is requested and the time the data page is displayed |
US7243122B2 (en) * | 1998-09-01 | 2007-07-10 | Lucent Technologies Inc. | Computer implemented method and apparatus for fulfilling a request for information content with a user-selectable version of a file containing that information content |
US20050065999A1 (en) * | 1998-09-01 | 2005-03-24 | Swarup Acharya | Computer implemented method and apparatus for fulfilling a request for information content with a user-selectable version of a file containing that information content |
US20020026563A1 (en) * | 1999-01-25 | 2002-02-28 | John T. Chamberlain | Cache override control in an apparatus for caching dynamic content |
US20020194382A1 (en) * | 2001-06-04 | 2002-12-19 | Kausik Balas Natarajan | Method and system for efficient and automated version management of embedded objects in web documents |
US7376790B2 (en) * | 2001-06-12 | 2008-05-20 | Network Appliance, Inc. | Caching media data using content sensitive object identifiers |
US20030236857A1 (en) * | 2002-03-07 | 2003-12-25 | International Business Machines Corporation | Network service system and program using data processing |
US7200756B2 (en) * | 2002-06-25 | 2007-04-03 | Microsoft Corporation | Base cryptographic service provider (CSP) methods and apparatuses |
US20120271905A1 (en) * | 2004-03-31 | 2012-10-25 | Qurio Holdings, Inc. | Proxy caching in a photosharing peer-to-peer network to improve guest image viewing performance |
US20130110906A1 (en) * | 2011-11-02 | 2013-05-02 | Microsoft Corporation | Browser cache assist for accessing web-based content |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9639629B1 (en) * | 2011-08-31 | 2017-05-02 | Instart Logic, Inc. | Accelerating the downloading of content to an application |
US20140108590A1 (en) * | 2012-10-11 | 2014-04-17 | Simon Hunt | Efficient shared image deployment |
US11126418B2 (en) * | 2012-10-11 | 2021-09-21 | Mcafee, Llc | Efficient shared image deployment |
US20150295987A1 (en) * | 2012-10-26 | 2015-10-15 | Eutelsat S A | Method for the recovery of content corresponding to a url address by a client device |
US10523734B2 (en) * | 2012-10-26 | 2019-12-31 | Eutelsat S A | Method for the recovery of content corresponding to a URL address by a client device |
US20140337415A1 (en) * | 2013-01-25 | 2014-11-13 | Canon Kabushiki Kaisha | Communication apparatus, method for controlling the same, and program |
US9602579B2 (en) * | 2013-01-25 | 2017-03-21 | Canon Kabushiki Kaisha | Communication apparatus, method for controlling the same, and program |
US20150271739A1 (en) * | 2014-03-20 | 2015-09-24 | Canon Kabushiki Kaisha | Relay apparatus, communication apparatus, control methods thereof, system, and non-transitory computer-readable storage medium |
US20150271678A1 (en) * | 2014-03-20 | 2015-09-24 | Canon Kabushiki Kaisha | Relay apparatus, relay method, relay system, and non-transitory computer-readable storage medium |
US9554278B2 (en) * | 2014-03-20 | 2017-01-24 | Canon Kabushiki Kaisha | Relay apparatus, relay method, relay system, and non-transitory computer-readable storage medium |
US10158418B2 (en) * | 2014-03-20 | 2018-12-18 | Canon Kabushiki Kaisha | Relay apparatus, communication apparatus, control methods thereof, system, and non-transitory computer-readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
US8010670B2 (en) | 2011-08-30 |
US8291081B2 (en) | 2012-10-16 |
US20150264151A1 (en) | 2015-09-17 |
US9967359B2 (en) | 2018-05-08 |
US20050138176A1 (en) | 2005-06-23 |
US20120016931A1 (en) | 2012-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8291081B2 (en) | Meta-data based method for local cache utilization | |
US8224964B1 (en) | System and method of accessing a document efficiently through multi-tier web caching | |
US8812651B1 (en) | Systems and methods for client cache awareness | |
US8275790B2 (en) | System and method of accessing a document efficiently through multi-tier web caching | |
US7587398B1 (en) | System and method of accessing a document efficiently through multi-tier web caching | |
US9703885B2 (en) | Systems and methods for managing content variations in content delivery cache | |
US9158845B1 (en) | Reducing latencies in web page rendering | |
US7565423B1 (en) | System and method of accessing a document efficiently through multi-tier web caching | |
US20080235326A1 (en) | Methods and Apparatus for Accelerating Web Browser Caching | |
US20150058455A1 (en) | Apparatus and method for serving compressed content in a content delivery network | |
US20160241667A1 (en) | Extended http object cache system and method | |
US20150032803A1 (en) | Method and apparatus for reducing loading time of web pages | |
US20130339526A1 (en) | Method and system for generating and using an augmented bloom filter | |
US12086129B2 (en) | Distributed data processing | |
US20030191858A1 (en) | Response time of transformed documents based on caching and dynamic transformation | |
US20130246583A1 (en) | Method, system and server device for transmitting a digital resource in a client-server communication system | |
JP2002373108A (en) | Proxy device and proxy control system | |
JP2008293281A (en) | Cache device, server, cache system, cache method, and program | |
JP2005267435A (en) | Cache processing program and cache processing apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SLIPSTREAM DATA INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SINGH, AJIT;AHMED, SALMAAN;REEL/FRAME:028960/0354 Effective date: 20060307 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: BLACKBERRY LIMITED, ONTARIO Free format text: DISSOLUTION AGREEMENT;ASSIGNOR:SLIPSTREAM DATA INC.;REEL/FRAME:038883/0894 Effective date: 20151128 |
|
AS | Assignment |
Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103 Effective date: 20230511 |