Browse Prior Art Database

Resource-driven HTTP data stream buffering

IP.com Disclosure Number: IPCOM000124845D
Original Publication Date: 2005-May-10
Included in the Prior Art Database: 2005-May-10
Document File: 1 page(s) / 26K

Publishing Venue

IBM

Abstract

Resource-driven hypertext transfer protocol (HTTP) data stream buffering.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 72% of the total text.

Page 1 of 1

Resource-driven HTTP data stream buffering

Disclosed is an invention that provides a strategy for applying per-resource buffering/streaming strategies, allowing a single proxy server to selectively stream or buffer data based on the resource requested.

A Security Web Proxy such as Tivoli * Access Manager (TAM) WebSEAL intercepts HTTP data streams sent from application servers before forwarding to clients. This data is typically handled using one of two strategies:

1) Data is streamed directly from server to client through the proxy. As each byte is received, it is immediately forwarded to the client.

2) Various buffering schemes are used to optimize data transmission. Data is read into an internal buffer until the buffer is full and then the data is forwarded to the client.

A buffering strategy is generally preferred, because it provides a more efficient use of bandwidth. It also has positive proxy performance implications through improved use of system resources.

However, certain application or network conditions or behaviors can make the buffering strategy less attractive. Consider a client application that tunnels proprietary data across a persistent HTTP connection tunnel. The application server sends a byte every second. In the absence of a proxy the client will therefore receive a byte approximately every second. If a proxy is introduced that utilizes buffering, each byte will be intercepted at the proxy and added to the buffer. Only when the buffer is full...