US20130007212A1 - System and method to accelerate client/server interactions using predictive requests - Google Patents
System and method to accelerate client/server interactions using predictive requests Download PDFInfo
- Publication number
- US20130007212A1 US20130007212A1 US13/612,776 US201213612776A US2013007212A1 US 20130007212 A1 US20130007212 A1 US 20130007212A1 US 201213612776 A US201213612776 A US 201213612776A US 2013007212 A1 US2013007212 A1 US 2013007212A1
- Authority
- US
- United States
- Prior art keywords
- predictive
- response
- server
- requests
- client
- 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
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/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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- 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/563—Data redirection of data network streams
-
- 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/564—Enhancement of application control based on intercepted application data
-
- 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/565—Conversion or adaptation of application format or content
-
- 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]
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
Definitions
- the present disclosure relates to the field of data communications. More specifically, the present invention relates to the enhancement of perceived data throuput in a server/client communications system.
- a Client Agent receives or intercepts a request for data from a client application running on a user's computer.
- the Client Agent may analyze the request and may forward the request to a server having the requested data or to a Predictive Server associated with the server.
- the Predictive Server may analyze the request and forwards the request to the server.
- a response by the server to the request may be intercepted either by the Predictive Server, the Client Agent, or both.
- Either the Client Agent or the Predictive Server may generate one or a series of predictive requests for data to the server based on the content of the server's response.
- a response by the server to a predictive request may be stored either at the Client Agent or at the Predictive Server, and may be transmitted to the client application when the client application transmits a request for the data contained in the response.
- the Client Agent causes the client to accelerate his requests. This mode can be used separately or in conjunction with other modes.
- the Client Agent is referred to a “Predictive Agent”.
- FIG. 1 is a diagram showing a Client Agent and a Predictive Server according to the present invention
- FIG. 2 is a data flow diagram illustrating a first mode of the present invention
- FIG. 3 shows a hyper-text-markup-language (“HTML”) web page having URL's of the objects contained within the page;
- HTML hyper-text-markup-language
- FIG. 4 is a diagram illustrating compression of data on the channel between a Client
- FIG. 5 is a data flow diagram illustrating a second mode of the present invention.
- FIG. 6 is a data flow diagram illustrating a third mode of the present invention.
- the present invention is a system and method of enhancing perceived data throughput between a client application and a server containing data to be retrieved by the client.
- Predictive strategies implemented by intermediary elements such as a Client Agent and/or a Predictive Server, cause the server to transmit data likely to be requested by the client application, in advance of the client actually requesting the data or causes the client to accelerate his requests.
- the data may be stored either at the Client Agent or the Predictive Server, and is transmitted to the client application when a request for the data is actually transmitted by the client.
- Either the Client Agent or the Predictive Server may act as a predictive unit, that is, as a source of a predictive request.
- Either the Client Agent or the Predictive Server may act as a buffer unit, that is, as temporary storage for a server response.
- Requests for data and responses thereto may be transmitted in data packets or other common data structures used in connection with a dispersed data network. TCP/IP and/or any other communication protocols may be used as part of the present invention.
- the data transmitted using the system and method of the present invention may be text, graphics, audio or video. Requests for data may be transmitted using Hyper Text Transfer Protocol (“HTTP”) or any other data retrieval and exchange standard, currently known or yet to be devised.
- HTTP Hyper Text Transfer Protocol
- FIG. 1 there is illustrated a system according to the present invention, wherein a Client Agent 100 and a Predictive Server 200 are located along a data pathway between a client and a server.
- Both the Client Agent 100 and the Predictive Server 200 have a storage unit, 120 and 220 respectively, and both have an analyzer unit 110 and 210 respectively.
- the Client Agent 100 may be a software application residing on a computer in proximity with the computer where the client application is running, or even on the same computer as the client application.
- the Client Agent 100 may be an application also functioning as an Internet proxy for the client application.
- the Predicative Server 200 may be an application running on a computer in proximity with the server, or even on the same computer as the server application.
- a request for data from the server, generated by the client may follow a path from the client, through the Client Agent 100 (path 1 ), through the Predictive Server 200 (path 2 ) and to the server (path 3 ). Alternatively, the request may follow a path skipping either the Client Agent 100 (path 4 ) or the Predictive Server 200 (path 5 ), but not both.
- the Client Agent 100 or the Predictive Server 200 may not be a recipient of a request generated by the client or a response generated by the server, either may intercept and analyze a copy of the communication.
- the Client Agent or Server may analyze data packets passing by using a method known as sniffing the line, or any other equivalent method, and intercept those packets having a destination address value related to either the client or the server.
- a response from the server may follow a reverse path from that of the request evoking the response, or any other path illustrated in FIG. 1 .
- a Client Agent 100 or the Predictive Server 200 may not be a recipient of a response generated by the server, either may intercept and analyze a copy of the request.
- the transmission of a client's request or a server's response is regulated via the manipulation of source address and destination address values on the data packets comprising the data object, or by any other means presently known or not yet devised.
- a data packet transmitted by a client and addressed to a server may be intercepted by either the Client Agent 100 or the Predictive Server 200 , and re-addressed to have the destination address of a destination other than the server and a source address of the Agent, which intercepted the packet.
- the routing and/or re-addressing of data packets between different points on a dispersed network are well known.
- the present invention functions with all known and not yet devised methods of routing and/or readdressing data packets.
- FIG. 2 there is illustrated a data flow diagram for a first mode of the present invention where both a Client Agent 100 and a Predictive Server 200 are utilized.
- a client's request for data 310 is received by the Client Agent 100 , where a record of the request is made.
- the Client Agent 100 then forwards the request 320 to the Predictive Server 200 , where a record of the request is also made.
- the Predictive Server 200 then forwards the request 330 to the server from which a response is expected.
- the above-mentioned steps may be collectively referred to as Stage 1 , as shown in the FIG. 1 .
- Stage 1 ends and Stage 2 begins upon the server's receipt of the client's request.
- the server's response travels back through the Predictive Server 200 , where it is analyzed to determine one or a series of possible subsequent requests the client may transmit.
- one of the first responses by a server to a client's request for a web page contains a list of objects present within the page, and instructions as to how to retrieve these objects from the server (e.g. the objects'URLs).
- the Predictive Server 200 may derive the series of possible future client requests and generate a “prediction list” based on the list of page objects in the response.
- FIG. 3 shows a hyper-text-markup-language (“HTML”) web page having URL's of the objects contained within the page.
- the Predictive Server 200 forwards the response 350 to the Client Agent 100 and issues one or a series of predictive requests 331 , 332 . . . etc . . . , shown in FIG. 2 as dashed arrows, to the server.
- the predictive requests are based on the results of the analysis of the server's previous response. In the case where the original request is for a web page, the series of predictive requests will typically be URL's of the objects contained within the page.
- the server may issue predictive responses 341 , 342 . . . addressed to the Predictive Server 200 .
- the Predicative Server 200 may automatically forward the predictive responses to the Client Agent 100 , or the Predictive Server 200 may store the predictive responses in storage 220 and wait to receive a request from the Client Agent 100 for a specific response or set of responses before forwarding it.
- a Predictive Server 200 when a Predictive Server 200 receives any response from the server, it automatically forwards the response to the Client Agent 100 , in particular the first response 350 is immediately forwarded to the Client Agent.
- the client upon receiving a first response 360 from the server, compares the list of objects within the response against objects already stored locally, and issues a request 311 which it forward to the Client Agent 100 .
- the Predicative Agent 100 compares the request 311 against its own “predicative list” and against a list of already received predictive responses. If the predictive list does not have an entry for a predictive request corresponding to the client's request 311 , the Client Agent 100 forwards the request along, as shown by arrow 325 in FIG. 2 and described herein below.
- a predictive response corresponding to the requests 311 , 312 , 313 , 314 and 315 is on the predictive list and has already arrived 351 and 352 at the Client Agent 100 , the response is transmitted to the client, as shown by arrow 361 , 362 , 363 and 364 . If a corresponding predictive request is on the list, but no corresponding predictive response has yet arrived at the Client Agent 100 , the Client Agent 100 waits for the corresponding response to arrive and forwards it to the client upon receipt.
- Request 325 initiates stage three in FIG. 2 , which is similar to stages one and two that are described above. In the Predictive Server 200 a record of the request 325 is made.
- the Predictive Server 200 then forwards the request 335 to the server from which a response is expected.
- the server's response 345 travels back through the Predictive Server 200 , where it is analyzed to determine one or a series of possible subsequent requests the client may transmit.
- the Predictive Server 200 forwards the response 355 to the Client Agent 100 and issues one or a series of predictive requests 370 .
- the Client Agent 100 forwards the response 365 to the client and generates its own “predictive list” and the process continues, as it is described above.
- FIG. 4 shows a mode of the present invention where the Predictive Server 200 does not automatically forward to Client Agent 100 predictive responses received from the server 341 , 342 , as shown in FIG. 2 , but instead stores the predictive responses in storage 220 until a request 421 for the responses is received from the Client Agent 100 .
- the client upon receiving a first response 360 from the server, compares the list of objects within the response against objects already stored locally, and issues requests 411 , 412 , . . . 414 for only those objects not present locally.
- the client's set of issued requests 411 , 412 , . . . 414 may have fewer objects than contained in the response 360 when one or several of the objects listed in the response are already present locally at or near the client.
- the Predicative Agent 100 then forwards the set, or an equivalent representation of the set 421 , to the Predictive Server 200 . Thereby, the Predictive Server 200 only transmits those predictive responses 451 , 452 . . . 454 not already present locally at the client. Upon receiving the responses, the Client Agent 100 transfers them to the client 461 , 462 . . . 464 .
- the Client Agent 100 and the Predictive Server 200 may perform communication optimization techniques such as compression, protocol conversion, and partial information transfer on the connections (i.e. requests and responses) between the two.
- Many techniques and strategies are known and applicable to the present invention.
- the Client Agent 100 may combine several client requests into one request packet or a series of packets, as shown in FIG. 4 .
- the Client Agent 100 may convert a request containing a complete Uniform Resource Locator (“URL”) for an object into a smaller request with only a partial or relative URL. That is, the smaller URL contains only part of the instructions for retrieving an object from the server.
- URL Uniform Resource Locator
- the Predictive Server 200 is able to identify the source of the smaller request, namely the client, and the Predictive Server 200 has a record of the last response received by the client, the Predictive Server 200 is able to convert a request with a partial URL back into one with a complete URL which is in a form acceptable to the server.
- Agent 100 may also be compressed by combining several responses into one or a series of packets.
- Various compression routines may be applied data flowing from the Predictive Server 200 to the Client Agent.
- the Client Agent may decompress the data and forward it to the client in its original form. Compression and decompression of data is well known, and any methods known today or yet to be devised may be applied as part of the present invention.
- the predictive responses are addressed directly to the Client Agent 100 , thereby bypassing the Predictive Server 200 .
- Each of the predictive requests sent by the Predictive Server 200 may contain a source address of the Client Agent 100 .
- the server's response to the predictive request, the predictive response is addressed directly to the Client Agent 100 .
- the Client Agent's 100 “predictive list” of requests may be derived from the response, in the same manner as a list was derived by the Predictive Server 200 , or the list may be a duplicate of the list produced by the Predictive Server 200 .
- the Predictive Server 200 may transmit its prediction list to the Client Agent 100 .
- the present invention may utilize any method or protocol of transmission, currently known or yet to be devised.
- FIG. 5 there is shown a data flow diagram for a mode of the present invention only utilizing a Client Agent 100 .
- a client's request 510 is received by a Client Agent 100 and sent 520 directly to a server.
- the server's response 530 to the request is intercepted by the Client Agent 100 and stripped of all information other than page formatting and the list of objects needed to be retrieved in order to complete the page, with a command to re-load all the objects after they are all retrieved, by using for example a Java Script.
- the client receives this modified and stripped down version of the response 540 , it checks against a list of locally stored objects to determine which objects need to be requested.
- the Client issues requests 511 A, 512 A .
- the Client Agent 100 forwards the request 521 - 524 to the server and responds to each of these requests with a pseudo or fake response 551 - 554 containing little or no data. While the client is receiving pseudo responses to its requests, the server is sending real responses to the request 531 - 534 to the Client Agent 100 . Once the client runs the reload script, the Client Agent 100 receives a new set of requests 511 B- 514 B from the client. The new set is just a copy of the previous set 511 A- 514 A, and the Client Agent 100 checks each incoming request for matching or corresponding response, which may have already arrived from the server.
- FIG. 6 there is a data flow diagram illustrating data flow of mode of the present invention where only a Predictive Server 200 is used. As part of this mode request 610 from Client is transferred 620 to Server, which issues a first response 630 . The Predictive Server generates or issues series of predictive requests 651 - 655 based on a server's first response 630 .
- the first response 630 is forwarded to the client 640 which checks to see which of the objects listed in the response are present locally, and then the client issues requests 611 - 614 for those objects listed in the response but not present locally.
- the requests 611 - 614 are received by the Predictive Server 200 and corresponding responses are sent to the client as soon at they are received by the Predictive Server 200 .
- the Predictive Server 200 issued predictive requests 651 - 655 at about the same time as the original response 640 was forwarded to the client, many of the responses for the requests 611 - 614 issued by the client should already be received 631 - 635 and be stored at the Predictive Server 200 storage 220 prior to the receipt of the client's requests 611 - 614 .
- Predictive Server 200 is able to respond immediately 641 - 644 to each such client's requests 611 - 614 respectively. It is appreciated that one or more steps of any of the methods described herein may be implemented in a different order than that shown while not departing from the spirit and scope of the invention.
- the present invention can be used in any client/server architecture, which architecture uses a systematic method in which the client retrieves data from the server (e.g. MS Exchange, Lotus Notes, SAP, . . . etc.).
- server e.g. MS Exchange, Lotus Notes, SAP, . . . etc.
Abstract
Description
- This is a utility patent application being filed in the U.S. as a non-provisional application for patent under Title 35 U.S.C. §100 et seq. and 37 C.F.R. §1.53(b) as a continuation of and claiming the benefit of the prior filing date afforded to co-pending and common inventorship U.S. patent application Ser. No. 09/788,545, which application claims the benefit under Title 35, U.S.C. §119(e) of U.S. provisional applications for patent that were filed on Feb. 22, 200 and assigned Ser. No. 60/183,818, Apr. 3, 2000 and assigned Ser. No. 60/194,050 and Apr. 11, 2000 and assigned Ser. No. 60/196,163, which applications are incorporated herein by reference in their entirety.
- The present disclosure relates to the field of data communications. More specifically, the present invention relates to the enhancement of perceived data throuput in a server/client communications system.
- Data communications systems based on a dispersed client/server architecture have become prevalent over the last decade. The most notable and extensive of these dispersed client/server communications systems I the Internet. The World Wide Web (the “Web”), a series of applications introduced in the early-to-mid 1990's which allow layman Internet users to access information residing on servers at all points of the globe, has caused the volume of Internet data traffic to increase to unprecedented levels. The explosive growth in Internet data traffic, which seems to have outpaced the rate of expansion of the Internet's infrastructure, has produced bottlenecks along
- As part of the present invention, a Client Agent receives or intercepts a request for data from a client application running on a user's computer. The Client Agent may analyze the request and may forward the request to a server having the requested data or to a Predictive Server associated with the server. The Predictive Server may analyze the request and forwards the request to the server. A response by the server to the request may be intercepted either by the Predictive Server, the Client Agent, or both. Either the Client Agent or the Predictive Server may generate one or a series of predictive requests for data to the server based on the content of the server's response. A response by the server to a predictive request may be stored either at the Client Agent or at the Predictive Server, and may be transmitted to the client application when the client application transmits a request for the data contained in the response. In another mode of the invention the Client Agent causes the client to accelerate his requests. This mode can be used separately or in conjunction with other modes.
- In the provisional patent applications (60/183,818; 60/194,050 and 60/196,163) the Client Agent is referred to a “Predictive Agent”.
- The present invention will be understood and appreciated more fully from the following detailed description taken in conjunction with the appended drawings in which:
-
FIG. 1 is a diagram showing a Client Agent and a Predictive Server according to the present invention; -
FIG. 2 is a data flow diagram illustrating a first mode of the present invention; -
FIG. 3 shows a hyper-text-markup-language (“HTML”) web page having URL's of the objects contained within the page; -
FIG. 4 is a diagram illustrating compression of data on the channel between a Client - Agent and a Predictive Server;
-
FIG. 5 is a data flow diagram illustrating a second mode of the present invention; and -
FIG. 6 is a data flow diagram illustrating a third mode of the present invention. - The present invention is a system and method of enhancing perceived data throughput between a client application and a server containing data to be retrieved by the client. Predictive strategies implemented by intermediary elements such as a Client Agent and/or a Predictive Server, cause the server to transmit data likely to be requested by the client application, in advance of the client actually requesting the data or causes the client to accelerate his requests. The data may be stored either at the Client Agent or the Predictive Server, and is transmitted to the client application when a request for the data is actually transmitted by the client. Either the Client Agent or the Predictive Server may act as a predictive unit, that is, as a source of a predictive request. Either the Client Agent or the Predictive Server may act as a buffer unit, that is, as temporary storage for a server response.
- Requests for data and responses thereto may be transmitted in data packets or other common data structures used in connection with a dispersed data network. TCP/IP and/or any other communication protocols may be used as part of the present invention. The data transmitted using the system and method of the present invention may be text, graphics, audio or video. Requests for data may be transmitted using Hyper Text Transfer Protocol (“HTTP”) or any other data retrieval and exchange standard, currently known or yet to be devised.
- Turning now to
FIG. 1 , there is illustrated a system according to the present invention, wherein aClient Agent 100 and aPredictive Server 200 are located along a data pathway between a client and a server. Both theClient Agent 100 and thePredictive Server 200 have a storage unit, 120 and 220 respectively, and both have ananalyzer unit - The
Client Agent 100 may be a software application residing on a computer in proximity with the computer where the client application is running, or even on the same computer as the client application. TheClient Agent 100 may be an application also functioning as an Internet proxy for the client application. - The Predicative Server 200 may be an application running on a computer in proximity with the server, or even on the same computer as the server application.
- A request for data from the server, generated by the client, may follow a path from the client, through the Client Agent 100 (path 1), through the Predictive Server 200 (path 2) and to the server (path 3). Alternatively, the request may follow a path skipping either the Client Agent 100 (path 4) or the Predictive Server 200 (path 5), but not both. Although the
Client Agent 100 or thePredictive Server 200 may not be a recipient of a request generated by the client or a response generated by the server, either may intercept and analyze a copy of the communication. The Client Agent or Server may analyze data packets passing by using a method known as sniffing the line, or any other equivalent method, and intercept those packets having a destination address value related to either the client or the server. - A response from the server may follow a reverse path from that of the request evoking the response, or any other path illustrated in
FIG. 1 . Although aClient Agent 100 or thePredictive Server 200 may not be a recipient of a response generated by the server, either may intercept and analyze a copy of the request. - The transmission of a client's request or a server's response is regulated via the manipulation of source address and destination address values on the data packets comprising the data object, or by any other means presently known or not yet devised. For example, a data packet transmitted by a client and addressed to a server may be intercepted by either the
Client Agent 100 or thePredictive Server 200, and re-addressed to have the destination address of a destination other than the server and a source address of the Agent, which intercepted the packet. Thus, altering the path of the packet. The routing and/or re-addressing of data packets between different points on a dispersed network are well known. The present invention functions with all known and not yet devised methods of routing and/or readdressing data packets. - The system and method of the present invention may take one of several embodiments and may be implemented according to one of several methodologies, examples of which are described below:
- Turning now to
FIG. 2 , there is illustrated a data flow diagram for a first mode of the present invention where both aClient Agent 100 and aPredictive Server 200 are utilized. As part of the first mode of the present invention, a client's request fordata 310 is received by theClient Agent 100, where a record of the request is made. TheClient Agent 100 then forwards therequest 320 to thePredictive Server 200, where a record of the request is also made. ThePredictive Server 200 then forwards therequest 330 to the server from which a response is expected. The above-mentioned steps may be collectively referred to asStage 1, as shown in theFIG. 1 . -
Stage 1 ends andStage 2 begins upon the server's receipt of the client's request. After analyzing the request and assuming the server possesses in its storage device the requested data or web page, it generates and transmits aresponse 340 corresponding to the request. The server's response travels back through thePredictive Server 200, where it is analyzed to determine one or a series of possible subsequent requests the client may transmit. Typically, one of the first responses by a server to a client's request for a web page contains a list of objects present within the page, and instructions as to how to retrieve these objects from the server (e.g. the objects'URLs). ThePredictive Server 200 may derive the series of possible future client requests and generate a “prediction list” based on the list of page objects in the response.FIG. 3 shows a hyper-text-markup-language (“HTML”) web page having URL's of the objects contained within the page. ThePredictive Server 200 forwards theresponse 350 to theClient Agent 100 and issues one or a series ofpredictive requests FIG. 2 as dashed arrows, to the server. The predictive requests are based on the results of the analysis of the server's previous response. In the case where the original request is for a web page, the series of predictive requests will typically be URL's of the objects contained within the page. - In response to the predictive requests, the server may issue
predictive responses Predictive Server 200. ThePredicative Server 200 may automatically forward the predictive responses to theClient Agent 100, or thePredictive Server 200 may store the predictive responses instorage 220 and wait to receive a request from theClient Agent 100 for a specific response or set of responses before forwarding it. In the example ofFIG. 2 , when aPredictive Server 200 receives any response from the server, it automatically forwards the response to theClient Agent 100, in particular thefirst response 350 is immediately forwarded to the Client Agent. - The client, upon receiving a
first response 360 from the server, compares the list of objects within the response against objects already stored locally, and issues arequest 311 which it forward to theClient Agent 100. ThePredicative Agent 100 compares therequest 311 against its own “predicative list” and against a list of already received predictive responses. If the predictive list does not have an entry for a predictive request corresponding to the client'srequest 311, theClient Agent 100 forwards the request along, as shown byarrow 325 inFIG. 2 and described herein below. If a predictive response corresponding to therequests Client Agent 100, the response is transmitted to the client, as shown byarrow Client Agent 100, theClient Agent 100 waits for the corresponding response to arrive and forwards it to the client upon receipt.Request 325 initiates stage three inFIG. 2 , which is similar to stages one and two that are described above. In the Predictive Server 200 a record of therequest 325 is made. ThePredictive Server 200 then forwards therequest 335 to the server from which a response is expected. The server'sresponse 345 travels back through thePredictive Server 200, where it is analyzed to determine one or a series of possible subsequent requests the client may transmit. ThePredictive Server 200 forwards theresponse 355 to theClient Agent 100 and issues one or a series ofpredictive requests 370. TheClient Agent 100 forwards theresponse 365 to the client and generates its own “predictive list” and the process continues, as it is described above. -
FIG. 4 shows a mode of the present invention where thePredictive Server 200 does not automatically forward toClient Agent 100 predictive responses received from theserver FIG. 2 , but instead stores the predictive responses instorage 220 until arequest 421 for the responses is received from theClient Agent 100. The client, upon receiving afirst response 360 from the server, compares the list of objects within the response against objects already stored locally, andissues requests requests response 360 when one or several of the objects listed in the response are already present locally at or near the client. ThePredicative Agent 100 then forwards the set, or an equivalent representation of theset 421, to thePredictive Server 200. Thereby, thePredictive Server 200 only transmits thosepredictive responses Client Agent 100 transfers them to theclient - As part of the present invention, the
Client Agent 100 and thePredictive Server 200 may perform communication optimization techniques such as compression, protocol conversion, and partial information transfer on the connections (i.e. requests and responses) between the two. Many techniques and strategies are known and applicable to the present invention. For example, theClient Agent 100 may combine several client requests into one request packet or a series of packets, as shown inFIG. 4 . Additionally, theClient Agent 100 may convert a request containing a complete Uniform Resource Locator (“URL”) for an object into a smaller request with only a partial or relative URL. That is, the smaller URL contains only part of the instructions for retrieving an object from the server. However, because thePredictive Server 200 is able to identify the source of the smaller request, namely the client, and thePredictive Server 200 has a record of the last response received by the client, thePredictive Server 200 is able to convert a request with a partial URL back into one with a complete URL which is in a form acceptable to the server. - Responses to client requests, transmitted from the
Predictive Server 200 to the Client -
Agent 100 may also be compressed by combining several responses into one or a series of packets. Various compression routines may be applied data flowing from thePredictive Server 200 to the Client Agent. Upon receipt of compressed data, the Client Agent may decompress the data and forward it to the client in its original form. Compression and decompression of data is well known, and any methods known today or yet to be devised may be applied as part of the present invention. - In an alternate embodiment of the present invention, the predictive responses are addressed directly to the
Client Agent 100, thereby bypassing thePredictive Server 200. Each of the predictive requests sent by thePredictive Server 200 may contain a source address of theClient Agent 100. When a predictive request contains the source address of theClient Agent 100, the server's response to the predictive request, the predictive response, is addressed directly to theClient Agent 100. - The Client Agent's 100 “predictive list” of requests may be derived from the response, in the same manner as a list was derived by the
Predictive Server 200, or the list may be a duplicate of the list produced by thePredictive Server 200. There are many well-known methods by which thePredictive Server 200 may transmit its prediction list to theClient Agent 100. The present invention may utilize any method or protocol of transmission, currently known or yet to be devised. - Turning now to
FIG. 5 , there is shown a data flow diagram for a mode of the present invention only utilizing aClient Agent 100. As part of the illustrated mode, a client'srequest 510 is received by aClient Agent 100 and sent 520 directly to a server. The server'sresponse 530 to the request is intercepted by theClient Agent 100 and stripped of all information other than page formatting and the list of objects needed to be retrieved in order to complete the page, with a command to re-load all the objects after they are all retrieved, by using for example a Java Script. When the client receives this modified and stripped down version of theresponse 540, it checks against a list of locally stored objects to determine which objects need to be requested. The Client issuesrequests Client Agent 100 forwards the request 521-524 to the server and responds to each of these requests with a pseudo or fake response 551-554 containing little or no data. While the client is receiving pseudo responses to its requests, the server is sending real responses to the request 531-534 to theClient Agent 100. Once the client runs the reload script, theClient Agent 100 receives a new set ofrequests 511B-514B from the client. The new set is just a copy of theprevious set 511A-514A, and theClient Agent 100 checks each incoming request for matching or corresponding response, which may have already arrived from the server. In the event a response has arrived, theClient Agent 100 forwards the response 541-544 to the client. If a corresponding response has not arrived, the Predictive Server waits and forwards the response to the client as soon as it is received. This mode of the invention may be practiced utilizing only aPredictive Server 200 instead of aClient Agent 100. Mode Three-Predictive Server Turning now toFIG. 6 , there is a data flow diagram illustrating data flow of mode of the present invention where only aPredictive Server 200 is used. As part of thismode request 610 from Client is transferred 620 to Server, which issues afirst response 630. The Predictive Server generates or issues series of predictive requests 651-655 based on a server'sfirst response 630. Thefirst response 630 is forwarded to theclient 640 which checks to see which of the objects listed in the response are present locally, and then the client issues requests 611-614 for those objects listed in the response but not present locally. The requests 611-614 are received by thePredictive Server 200 and corresponding responses are sent to the client as soon at they are received by thePredictive Server 200. Given that thePredictive Server 200 issued predictive requests 651-655 at about the same time as theoriginal response 640 was forwarded to the client, many of the responses for the requests 611-614 issued by the client should already be received 631-635 and be stored at thePredictive Server 200storage 220 prior to the receipt of the client's requests 611-614. Therefore,Predictive Server 200 is able to respond immediately 641-644 to each such client's requests 611-614 respectively. It is appreciated that one or more steps of any of the methods described herein may be implemented in a different order than that shown while not departing from the spirit and scope of the invention. - While the methods and apparatus disclosed herein may or may not have been described with reference to specific hardware or software, the methods and apparatus have been described in a manner sufficient to enable persons of ordinary skill in the art to readily adapt commercially available hardware and software as may be needed to reduce any of the embodiments of the present invention to practice without undue experimentation and using conventional techniques.
- Those skilled in the art will appreciate that the present invention can be used in any client/server architecture, which architecture uses a systematic method in which the client retrieves data from the server (e.g. MS Exchange, Lotus Notes, SAP, . . . etc.).
- While the present invention has been described with reference to a few specific embodiments, the description is intended to be illustrative of the invention as a whole and is not to be construed as limiting the invention to the embodiments shown. It is appreciated that various modifications may occur to those skilled in the art that, while not specifically shown herein, are nevertheless within the true spirit and scope of the invention.
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/612,776 US20130007212A1 (en) | 2000-02-22 | 2012-09-12 | System and method to accelerate client/server interactions using predictive requests |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18381800P | 2000-02-22 | 2000-02-22 | |
US19405000P | 2000-04-03 | 2000-04-03 | |
US19616300P | 2000-04-11 | 2000-04-11 | |
US09/788,545 US8291007B2 (en) | 2000-02-22 | 2001-02-21 | System and method to accelerate client/server interactions using predictive requests |
US13/612,776 US20130007212A1 (en) | 2000-02-22 | 2012-09-12 | System and method to accelerate client/server interactions using predictive requests |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/788,545 Continuation US8291007B2 (en) | 2000-02-22 | 2001-02-21 | System and method to accelerate client/server interactions using predictive requests |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130007212A1 true US20130007212A1 (en) | 2013-01-03 |
Family
ID=27391749
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/788,545 Expired - Fee Related US8291007B2 (en) | 2000-02-22 | 2001-02-21 | System and method to accelerate client/server interactions using predictive requests |
US13/612,776 Abandoned US20130007212A1 (en) | 2000-02-22 | 2012-09-12 | System and method to accelerate client/server interactions using predictive requests |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/788,545 Expired - Fee Related US8291007B2 (en) | 2000-02-22 | 2001-02-21 | System and method to accelerate client/server interactions using predictive requests |
Country Status (6)
Country | Link |
---|---|
US (2) | US8291007B2 (en) |
EP (1) | EP1277118B1 (en) |
AT (1) | ATE412218T1 (en) |
AU (1) | AU2001235937A1 (en) |
DE (1) | DE60136270D1 (en) |
WO (1) | WO2001063420A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10341400B2 (en) * | 2013-05-15 | 2019-07-02 | Simeon La Barrie | System and method for signal and data routing |
US20210256087A1 (en) * | 2013-11-21 | 2021-08-19 | Google Llc | Speeding up document loading |
Families Citing this family (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8065399B2 (en) | 2000-04-17 | 2011-11-22 | Circadence Corporation | Automated network infrastructure test and diagnostic system and method therefor |
US20110128972A1 (en) * | 2000-04-17 | 2011-06-02 | Randy Thornton | Peer to peer dynamic network link acceleration |
AU2001253613A1 (en) * | 2000-04-17 | 2001-10-30 | Circadence Corporation | System and method for shifting functionality between multiple web servers |
US8195823B2 (en) | 2000-04-17 | 2012-06-05 | Circadence Corporation | Dynamic network link acceleration |
US8898340B2 (en) * | 2000-04-17 | 2014-11-25 | Circadence Corporation | Dynamic network link acceleration for network including wireless communication devices |
US8996705B2 (en) | 2000-04-17 | 2015-03-31 | Circadence Corporation | Optimization of enhanced network links |
US7571446B2 (en) * | 2001-04-19 | 2009-08-04 | International Business Machines Corporation | Server, computer system, object management method, server control method, computer program |
JP4217391B2 (en) * | 2001-07-30 | 2009-01-28 | キヤノン株式会社 | Information acquisition system, information processing apparatus, method, program, and medium |
US7603452B1 (en) * | 2002-03-26 | 2009-10-13 | Symantec Corporation | Networked computer environment assurance system and method |
US7953820B2 (en) * | 2002-09-11 | 2011-05-31 | Hughes Network Systems, Llc | Method and system for providing enhanced performance of web browsing |
US8176186B2 (en) | 2002-10-30 | 2012-05-08 | Riverbed Technology, Inc. | Transaction accelerator for client-server communications systems |
US8069225B2 (en) * | 2003-04-14 | 2011-11-29 | Riverbed Technology, Inc. | Transparent client-server transaction accelerator |
US7120666B2 (en) | 2002-10-30 | 2006-10-10 | Riverbed Technology, Inc. | Transaction accelerator for client-server communication systems |
US8364815B2 (en) | 2005-03-18 | 2013-01-29 | Riverbed Technology, Inc. | Reliability and availability of distributed servers |
US8473620B2 (en) * | 2003-04-14 | 2013-06-25 | Riverbed Technology, Inc. | Interception of a cloud-based communication connection |
US7085762B2 (en) | 2003-05-22 | 2006-08-01 | International Business Machines Corporation | Methods, systems and computer program products for web services access of analytical models |
EP1515233A3 (en) * | 2003-08-06 | 2007-03-14 | Matsushita Electric Industrial Co., Ltd. | Method, server and client for reducing processing time in synchronous communication in a client-server distributed system |
US7853699B2 (en) * | 2005-03-15 | 2010-12-14 | Riverbed Technology, Inc. | Rules-based transaction prefetching using connection end-point proxies |
US8606876B2 (en) * | 2004-02-11 | 2013-12-10 | Flash Networks Ltd. | Method and system for accelerating data communication that is using multipart |
US7487145B1 (en) * | 2004-06-22 | 2009-02-03 | Google Inc. | Method and system for autocompletion using ranked results |
US7836044B2 (en) * | 2004-06-22 | 2010-11-16 | Google Inc. | Anticipated query generation and processing in a search engine |
US7499940B1 (en) * | 2004-11-11 | 2009-03-03 | Google Inc. | Method and system for URL autocompletion using ranked results |
US20060106769A1 (en) | 2004-11-12 | 2006-05-18 | Gibbs Kevin A | Method and system for autocompletion for languages having ideographs and phonetic characters |
WO2006066613A1 (en) | 2004-12-24 | 2006-06-29 | Telecom Italia S.P.A. | Method of optimising web page access in wireless networks |
US10064540B2 (en) * | 2005-02-02 | 2018-09-04 | Intuitive Surgical Operations, Inc. | Visualization apparatus for transseptal access |
EP1844612B1 (en) * | 2005-02-04 | 2017-05-10 | Barco NV | Method and device for image and video transmission over low-bandwidth and high-latency transmission channels |
US20060248194A1 (en) | 2005-03-18 | 2006-11-02 | Riverbed Technology, Inc. | Connection forwarding |
WO2006112844A1 (en) * | 2005-04-18 | 2006-10-26 | Riverbed Technology, Inc. | Transparent client-server transaction accelerator |
US9692725B2 (en) * | 2005-05-26 | 2017-06-27 | Citrix Systems, Inc. | Systems and methods for using an HTTP-aware client agent |
US8583827B2 (en) * | 2005-05-26 | 2013-11-12 | Citrix Systems, Inc. | Dynamic data optimization in data network |
US8943304B2 (en) | 2006-08-03 | 2015-01-27 | Citrix Systems, Inc. | Systems and methods for using an HTTP-aware client agent |
US8478986B2 (en) * | 2005-08-10 | 2013-07-02 | Riverbed Technology, Inc. | Reducing latency of split-terminated secure communication protocol sessions |
US8438628B2 (en) * | 2005-08-10 | 2013-05-07 | Riverbed Technology, Inc. | Method and apparatus for split-terminating a secure network connection, with client authentication |
US8010523B2 (en) | 2005-12-30 | 2011-08-30 | Google Inc. | Dynamic search box for web browser |
US8782393B1 (en) | 2006-03-23 | 2014-07-15 | F5 Networks, Inc. | Accessing SSL connection data by a third-party |
US7894820B2 (en) * | 2006-05-01 | 2011-02-22 | Intel Corporation | Channel feedback using channel state predictions based also on delays |
US7778599B2 (en) * | 2006-05-01 | 2010-08-17 | Intel Corporation | Aggregated channel feedback |
US8463843B2 (en) * | 2006-05-26 | 2013-06-11 | Riverbed Technology, Inc. | Throttling of predictive ACKs in an accelerated network communication system |
US8615562B1 (en) * | 2006-12-29 | 2013-12-24 | Google Inc. | Proxy for tolerating faults in high-security systems |
US8312032B2 (en) | 2008-07-10 | 2012-11-13 | Google Inc. | Dictionary suggestions for partial user entries |
US8707043B2 (en) * | 2009-03-03 | 2014-04-22 | Riverbed Technology, Inc. | Split termination of secure communication sessions with mutual certificate-based authentication |
WO2010139277A1 (en) | 2009-06-03 | 2010-12-09 | Google Inc. | Autocompletion for partially entered query |
US8489685B2 (en) | 2009-07-17 | 2013-07-16 | Aryaka Networks, Inc. | Application acceleration as a service system and method |
US8700892B2 (en) | 2010-03-19 | 2014-04-15 | F5 Networks, Inc. | Proxy SSL authentication in split SSL for client-side proxy agent resources with content insertion |
US8473688B2 (en) | 2010-03-26 | 2013-06-25 | Microsoft Corporation | Anticipatory response pre-caching |
US9021047B2 (en) | 2010-07-31 | 2015-04-28 | Unwired Planet, Llc | Method and system for delivering embedded objects in a webpage to a user agent using a network device |
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 |
US8612550B2 (en) | 2011-02-07 | 2013-12-17 | Microsoft Corporation | Proxy-based cache content distribution and affinity |
US8612418B2 (en) * | 2011-07-14 | 2013-12-17 | Google Inc. | Mobile web browser for pre-loading web pages |
US8874641B1 (en) * | 2011-09-13 | 2014-10-28 | Amazon Technologies, Inc. | Speculative generation of network page components |
US9122870B2 (en) * | 2011-09-21 | 2015-09-01 | SunStone Information Defense Inc. | Methods and apparatus for validating communications in an open architecture system |
CA2849162C (en) * | 2011-09-21 | 2016-12-20 | David K. Ford | Methods and apparatus for validating communications in an open architecture system |
US9037926B2 (en) * | 2012-06-07 | 2015-05-19 | International Business Machines Corporation | Background buffering of content updates |
US9246998B2 (en) | 2012-10-16 | 2016-01-26 | Microsoft Technology Licensing, Llc | Load balancer bypass |
US9654604B2 (en) * | 2012-11-22 | 2017-05-16 | Intel Corporation | Apparatus, system and method of controlling data flow over a communication network using a transfer response |
US9094481B2 (en) * | 2013-04-15 | 2015-07-28 | Seven Networks, Inc. | Adaptive downloading or streaming to conserve mobile device or network resources |
US9565233B1 (en) | 2013-08-09 | 2017-02-07 | Google Inc. | Preloading content for requesting applications |
IL241947A (en) * | 2015-10-07 | 2016-07-31 | Giraffic Technologies Ltd | Multi-request aggregation |
US9942312B1 (en) * | 2016-12-16 | 2018-04-10 | Zoomdata, Inc. | System and method for facilitating load reduction at a landing zone |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802292A (en) * | 1995-04-28 | 1998-09-01 | Digital Equipment Corporation | Method for predictive prefetching of information over a communications network |
US6721780B1 (en) * | 1999-11-09 | 2004-04-13 | Fireclick, Inc. | Predictive pre-download of network objects |
US7047485B1 (en) * | 1999-11-10 | 2006-05-16 | International Business Machines Corporation | Intelligent pre-caching on a network |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5715445A (en) * | 1994-09-02 | 1998-02-03 | Wolfe; Mark A. | Document retrieval system employing a preloading procedure |
US5978841A (en) * | 1996-03-08 | 1999-11-02 | Berger; Louis | Look ahead caching process for improved information retrieval response time by caching bodies of information before they are requested by the user |
US5918013A (en) * | 1996-06-03 | 1999-06-29 | Webtv Networks, Inc. | Method of transcoding documents in a network environment using a proxy server |
US6128667A (en) * | 1996-11-12 | 2000-10-03 | Elfnet, Inc. | System and method for deferred resolution hypertext links |
US6807570B1 (en) * | 1997-01-21 | 2004-10-19 | International Business Machines Corporation | Pre-loading of web pages corresponding to designated links in HTML |
US5878223A (en) * | 1997-05-07 | 1999-03-02 | International Business Machines Corporation | System and method for predictive caching of information pages |
US6038601A (en) * | 1997-07-21 | 2000-03-14 | Tibco, Inc. | Method and apparatus for storing and delivering documents on the internet |
US6393526B1 (en) * | 1997-10-28 | 2002-05-21 | Cache Plan, Inc. | Shared cache parsing and pre-fetch |
US6510469B1 (en) * | 1998-05-13 | 2003-01-21 | Compaq Information Technologies Group,L.P. | Method and apparatus for providing accelerated content delivery over a network |
US6098064A (en) * | 1998-05-22 | 2000-08-01 | Xerox Corporation | Prefetching and caching documents according to probability ranked need S list |
US6463509B1 (en) * | 1999-01-26 | 2002-10-08 | Motive Power, Inc. | Preloading data in a cache memory according to user-specified preload criteria |
US6728726B1 (en) * | 1999-03-05 | 2004-04-27 | Microsoft Corporation | Prefetching and caching persistent objects |
-
2001
- 2001-02-21 US US09/788,545 patent/US8291007B2/en not_active Expired - Fee Related
- 2001-02-22 DE DE60136270T patent/DE60136270D1/en not_active Expired - Lifetime
- 2001-02-22 WO PCT/IL2001/000169 patent/WO2001063420A1/en active Application Filing
- 2001-02-22 AT AT01908080T patent/ATE412218T1/en not_active IP Right Cessation
- 2001-02-22 EP EP01908080A patent/EP1277118B1/en not_active Expired - Lifetime
- 2001-02-22 AU AU2001235937A patent/AU2001235937A1/en not_active Abandoned
-
2012
- 2012-09-12 US US13/612,776 patent/US20130007212A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802292A (en) * | 1995-04-28 | 1998-09-01 | Digital Equipment Corporation | Method for predictive prefetching of information over a communications network |
US6721780B1 (en) * | 1999-11-09 | 2004-04-13 | Fireclick, Inc. | Predictive pre-download of network objects |
US7047485B1 (en) * | 1999-11-10 | 2006-05-16 | International Business Machines Corporation | Intelligent pre-caching on a network |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10341400B2 (en) * | 2013-05-15 | 2019-07-02 | Simeon La Barrie | System and method for signal and data routing |
US20210256087A1 (en) * | 2013-11-21 | 2021-08-19 | Google Llc | Speeding up document loading |
US11809511B2 (en) * | 2013-11-21 | 2023-11-07 | Google Llc | Speeding up document loading |
Also Published As
Publication number | Publication date |
---|---|
EP1277118B1 (en) | 2008-10-22 |
ATE412218T1 (en) | 2008-11-15 |
DE60136270D1 (en) | 2008-12-04 |
EP1277118A1 (en) | 2003-01-22 |
US20020023145A1 (en) | 2002-02-21 |
EP1277118A4 (en) | 2004-03-17 |
WO2001063420A1 (en) | 2001-08-30 |
AU2001235937A1 (en) | 2001-09-03 |
US8291007B2 (en) | 2012-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20130007212A1 (en) | System and method to accelerate client/server interactions using predictive requests | |
US8024484B2 (en) | Caching signatures | |
US8131823B2 (en) | System and method for reading ahead of content | |
US6947440B2 (en) | System and method for internet page acceleration including multicast transmissions | |
US8176183B2 (en) | System and a method for accelerating communication of TCP/IP based content | |
US5852717A (en) | Performance optimizations for computer networks utilizing HTTP | |
US6249787B1 (en) | Method and apparatus for transmitting images and other objects over a computer network system | |
US6892218B2 (en) | Extending network services using mobile agents | |
US6463447B2 (en) | Optimizing bandwidth consumption for document distribution over a multicast enabled wide area network | |
RU2210871C2 (en) | Distribution system and method for object pre- selection | |
US8176164B1 (en) | Method and system for managing network traffic | |
US20020002625A1 (en) | System and method for reformatting data traffic | |
JP2004164630A (en) | Client/server communication system | |
KR20040044182A (en) | System and method for increasing the effective bandwidth of a communications network | |
HU227369B1 (en) | A method, apparatus and computer program for reducing data transmitted over an external communication link from a first application resident in a first computer to a second application resident in a second computer | |
US20020059463A1 (en) | Method and system for accelerating internet access through data compression | |
US9967331B1 (en) | Method, intermediate device and computer program code for maintaining persistency | |
MXPA00001233A (en) | A distributed system and method for prefetching objects | |
JP2002111779A (en) | Data transmission method and data transmission system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FLASH NETWORKS LTD, ISRAEL Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ORR, MICHAEL;AV-RON, BOAZ;SEGALL, UDI;AND OTHERS;SIGNING DATES FROM 20010220 TO 20010304;REEL/FRAME:033280/0337 |
|
AS | Assignment |
Owner name: KREOS CAPITAL IV (EXPERT FUND) LIMITED, JERSEY Free format text: SECURITY INTEREST;ASSIGNOR:FLASH NETWORKS LTD.;REEL/FRAME:033558/0495 Effective date: 20140812 Owner name: MIZRAHI TEFAHOT BANK, LTD., ISRAEL Free format text: SECURITY INTEREST;ASSIGNOR:FLASH NETWORKS LTD.;REEL/FRAME:033558/0495 Effective date: 20140812 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |