Systems and methods for establishing quasi-persistent HTTP connections

• US 7,216,172 B2
• Filed: 09/25/2001
• Issued: 05/08/2007
• Est. Priority Date: 09/25/2001
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: WebEx Communications Incorporated (Cisco Systems, Inc.)
• Inventors: Martin, Christopher, Yang, Guanghong
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Refai; Ramsey
• Application Number:
  US09/963,216
• Publication Number:
  US 20030061355A1
• Time in Patent Office: 2,051 Days
• Field of Search: 709/227, 709/203, 709/225, 709/228
• US Class Current: 709/227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The present invention provides systems and methods that allow one or more quasi-persistent HTTP connections to be established between a client computer and server computer. The quasi-persistent HTTP connection(s) allow(s) data to be transferred between the client computer and the server computer without having to repeatedly set up and then terminate a HTTP connection between the client computer and the server computer each time the client computer and the server computer have data to send to one another. Two or more quasi-persistent HTTP connections can be established between a client computer and a server computer to form a bi-directional connection between the client computer and the server computer. The bi-directional connection significantly improves the speed and the efficiency of data transfer between the client computer and the server computer.

Claims

1. A method for generating a bi-directional communications link between a client and a server, the method comprising:

testing an HTTP proxy server;

to determine if the HTTP proxy server can communicate with said client using a quasi-persistent HTTP connection, by sending a test request comprising individual test data packets to the HTTP proxy server from said server;

determining if the HTTP proxy server forwards each of said individual test data packets from the test request to the client upon receipt of each of said individual test data packets from the server; and

if the HTTP proxy server does forward each of said individual data packets to the client upon receipt of each of said individual data packets, then generating at the server a response to a HTTP GET request having a first content-length value that is independent of the amount of data to be sent by the server in response to the HTTP GET request and large enough to establish a first quasi persistent HTTP connection between the client and the server via the HTTP proxy server; and

receiving at the server a HTTP POST request having a second content-length value that is large enough to establish a second quasi-persistent HTTP connection between the client and the server via the HTTP proxy server.

2. The method of claim 1 further comprising:

sending data from the server to the client over the first quasi-persistent HTTP connection, wherein the data can be sent from the server to the client without having to generate a new HTTP request.

3. The method of claim 1 further comprising:

receiving data from the client over the second quasi-persistent HTTP connection, wherein the data can be sent from the server to the client without having to generate a new HTTP request.

4. The method of claim 1 further comprising:

sending heartbeat data to the client over the first quasi-persistent HTTP connection.

5. The method of claim 1 further comprising:

receiving heartbeat data from the client over the second quasi-persistent HTTP connection.

6. The method of claim 1 wherein the first content-length value is at least 256 Kbytes.

7. The method of claim 1 wherein the second content-length value is at least 256 Kbytes.