PipeBoost™ is fully compliant with HTTP 1.1 specifications as described in Internet RFC 2616 (content compression is not always possible in HTTP 1.0). Two encoding formats are supported: deflate and gzip. Encapsulated in these encodings are the best publicly available general compression algorithms.

All configuration data is stored in IIS’s high-speed access repository: the metabase. The filter works transparently between server and client and is capable of compressing any (compressible) content being sent by a server, including error responses and content ranges. Why do we say compressible? For example, a well formed GIF or JPEG image is virtually uncompressible using these algorithms. Even though the application is capable of compressing this type of content, the performance gains are negligible.

The PipeBoost cache is validated against the original content on every request. PipeBoost always allows IIS and other installed filters to process a client’s request in order to ensure response and cache validity. The cached content is sent as is, while chunked transfer coding is used for dynamically generated data if it does not fit into the internal buffer.

To ease the job of administering the large volumes of content, we have developed the following:

• Configuration extension snap-in for Microsoft Management Console
• Error reporting via Windows event log
• Detailed real-time performance counters are made available to Microsoft Performance Monitor
• Static Content Analyzer application that helps tailor compression strategy to your environment
• Cache Performance Analyzer that expands monitoring and provides reporting functionality

Click here to see benchmark page.