Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Non-blocking I/O application proxy using HTTP protocols

IP.com Disclosure Number: IPCOM000010144D
Original Publication Date: 2002-Oct-25
Included in the Prior Art Database: 2002-Oct-25
Document File: 2 page(s) / 45K

Publishing Venue



This invention describes how an application proxy can be used to enforce HTTP protocols, enabling a client and remote server to communicate across a network, where the client and server are unaware of the use of HTTP. The first application proxy makes two persistent connections via an HTTP proxy to a second application proxy, using one connection to send all requests and the other to receive all of the responses, so each connection works in half-duplex mode. A unique key is sent from the first application proxy to the second application proxy, allowing it to maintain the pair of connections.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 2

Non-blocking I/O application proxy using HTTP protocols

This disclosure is for an application proxy to establish and maintain a connection to a destination server, using a pair of connections through a Hypertext Transfer Protocol (HTTP) proxy to maintain the HTTP request/response protocol flows. The key elements of this disclosure is that both connections through the HTTP proxy are started from same end point, both connections work in half-duplex mode and a unique key is sent on the first connection to pair it with the second.

    When a client makes a connection via an HTTP proxy to a server, the client usually implements and maintains the HTTP protocol request/response flows. Another option is for the client to use an application proxy to perform the HTTP flows on its behalf (see diagram below). When using this second approach, the application proxy has to work with another application proxy, the first one to wrap the application data in HTTP flows and a second one to unwrap the data before sending it on to the destination. The application proxy has to maintain the request/response flows that are expected by the HTTP proxy and when using a blocking I/O solution may need to analyze the application data to enforce the request/response flows.

    Using the following diagram to explain this in more detail, the client makes a persistent connection (A) to AP1 and sends it some application data. AP1 makes a persistent connection (B) to the HTTP proxy, wraps the application data in HTTP and sends it to the HTTP proxy. The HTTP proxy makes a persistent connection (C) to AP2 and sends it the application data (still wrapped in HTTP). AP2 makes a persistent connection (D) to the server, unwraps the application data and sends it to the server. Data is sent in both directions along the same connections. The application proxies analyze the application data...