Save money by reducing the bandwidth of your dynamic service
Compress in realtime the documents sent to serve the internet requests
Enhance the user experience by reducing the time necessary to display the web pages
Built for HTTP 1.1 pipelining, keeping the remote connection.
Do it all at blazing fast speed, with 100% reliability and small system overhead

Compress Content is designed and optimized for realtime compression of the result of application programming backends, such as ASP.NET. The solutions on the market usually don't compress the output produced by backends, because this involves a significant increase in CPU processing and lower efficiency. Today most of the web sites are powered by dynamic engines. Common web information systems, blogs, forums, CRMs: almost all of their parts are produced by programming backends. Compress Content is made to satisfy the requirements of today's web sites, where the logic and complexity are committed to a programming backend, and where the mission critical services require a 100% reliable QA modelled software, with the highest possible efficiency.

A sample schema workflow of Compress Content filter.

Compress Content works using an enhanced implementation of Zlib public library compiled with a highly efficient closed Runtime Library. This targets an optimized use of the modern cpu superscalar pipeline, offering 300% speedup compared to standard solutions.

Compress Content works keeping the remote connection alive, supporting the full HTTP 1.1 pipelining (some solutions convert the output with Chunked Encoding and break the TCP pipelining, lowering the overall TCP subsystem efficiency and requiring more bandwidth for every I/O request due to the TCP handshake).

Compress Content allows to save bandwidth by compressing all the dynamic webpages produced by your backend, such as ASP.NET, and it does it in realtime. If you wish, every document file sent from your webserver can be compressed. The web publisher that pays connectivity based on bandwidth consumption, can save money, because tipically the result of the compression is 300% lower document size compared to the original. All the users, especially those who use 56K modem connection, may feel better response time of the provided services, loading web pages in third of the time.

Our implementation is particularly designed for those who serve dynamic content. The algorithms are optimized for processing those typically small pieces of buffered data output of dynamic web pages (forum, chat, database driven web applications, etc.). So your company can save money both in bandwidth management and hardware resources.

The product was tested on Windows 2003 Server and IIS6.

Check a real scenario benchmark with a dynamic application.
Please check the downloads page to get the trial(*) version of the filter or to buy a license.

Filter your webserver content in realtime, by replacing a list of defined words.

Replacing the "bad words" with a pattern is ideal for communities, forums, blogs with children's audience. Using highly optimized routines, it works with the smallest demand of hardware resources.

You can download different "bad words" language dictionaries, and edit them by using a simple text editor.

The product was tested on Windows 2003 Server and IIS6.

Check this example page , which includes a pair of bad words.
Check the benchmark tested with twenty words, filtered in realtime.
Please check the downloads page to get the trial(*) version of the filter or to buy a license.

 

(*)limitations of the trial version: only 50% of the requests are processed and at 50% lower performance, compared to the native version. If you'd like to conduct a true benchmark test, please use the full version or contact the management. Thank you.