System and method for maintaining two-way asynchronous notification between a client and a web server

• US 20020099795A1
• Filed: 01/19/2001
• Published: 07/25/2002
• Est. Priority Date: 01/19/2001
• Status: Abandoned Application

• Current Assignee: Daniel Daou, Digital Orchid, Inc. (Sorteo Games, Inc.)
• Original Assignee: Digital Orchid, Inc. (Sorteo Games, Inc.)
• Inventors: Betros, Robert, Raad, Mansour
• Application Number:
  US09/766,439
• Publication Number:
  US 20020099795A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 67/01 Protocols
• 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 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A system and method for maintaining direct, two-way asynchronous communication between a client and a web server. An HTTP-compliant request is communicated from a client to a web server. The HTTP request is configured to initialize a CGI that operates within or in conjunction with the web server. A task, associated with the CGI, is executed in accordance with the HTTP request. The task is configured to perform the two-way asynchronous communication with the client until terminated by the client or the CGI. The task includes an operation in which client request data is listened for and read by the CGI through the web server. The task further includes an operation in which data is created and sent by the CGI to the client through the web server.

Claims

1. A method of maintaining two-way asynchronous communication between a client and a web server using a single HTTP transaction, comprising:

communicating an HTTP request from a client to a web server, wherein the HTTP request is configured to initialize a CGI that operates within or in conjunction with the web server; and

executing operations associated with the CGI, wherein the operations are configured to perform the two-way asynchronous communication with the client until terminated by the client or the CGI.

2. The method of claim 1, wherein executing operations includes receiving and processing data from the client.

3. The method of claim 2, wherein the data is compliant with the HTTP protocol or a protocol other than HTTP.

4. The method of claim 1, wherein executing operations includes creating and communicating data from the CGI to the client.

5. The method of claim 4, wherein the data is compliant with the HTTP protocol or a protocol other than HTTP.

6. The method of claim 1, wherein the client includes client-side logic configured to perform the two-way asynchronous communication with the CGI.

7. The method of claim 6, wherein the client-side logic is pre-installed on the client.

8. The method of claim 6, wherein the client-side logic is dynamically delivered to the client from the web server.

9. A system for maintaining two-way asynchronous communication between a client and a web server using a single HTTP transaction, comprising:

means for communicating an HTTP request from a client to a web server, wherein the HTTP request is configured to initialize a CGI that operates within or in conjunction with the web server; and

means for executing operations associated with the CGI, wherein the operations are configured to perform the two-way asynchronous communication with the client until terminated by the client or the CGI.

10. The method of claim 9, wherein the executing means includes means for receiving and processing data from the client.

11. The method of claim 10, wherein the data is compliant with the HTTP protocol or a protocol other than HTTP.

12. The method of claim 9, wherein the executing means includes means for creating and communicating data from the CGI to the client.

13. The method of claim 12, wherein the data is compliant with the HTTP protocol or a protocol other than HTTP.

14. The method of claim 9, wherein the communicating means includes client-side logic configured to perform the two-way asynchronous communication with the CGI.

15. The method of claim 14, wherein the client-side logic is pre-installed on the client.

16. The method of claim 14, wherein the client-side logic is dynamically delivered to the client from the web server.

17. The method of claim 16, wherein the client-side logic is delivered in the form of a Java™

applet.

18. The method of claim 16, wherein the client-side logic is delivered in the form of Macromedia Shockwave movie.

19. The method of claim 9, wherein the CGI is a servlet.