What's the purpose of realtime compression engine for IIS?
These days most of the websites are powered by backend engines, such as ASP.NET, ISAPI, PHP, ColdFusion and others. Using the compression as permitted in RFC2616 (HTTP1.1) we can reduce the size of output document sent to web users. Typically, the HTML document sizes are reduced by 300%. Other solutions on the market usually don't compress the result of ASP.NET or other backend engines, because of the system overhead. Our solution allows to bring realtime compression to dynamic backends, thanks to the ultra fast implementation of our closed algorithms.

Is it possible to further enhance the speed?
For the Compress Content we use a buffered method that implies some memory copy operations. Using a chunked method we could obtain faster throughput, but usually HTTP connections are closed after every I/O; so the overall better system performance is obtained using a fast buffered method, that keeps the HTTP pipelining enabled on every browser.

Who and how can save money with this solution?
Usually who offers internet services, pays a fee to the ISP, based on the consumed bandwidth. Considering that modern websites are powered by backends, and considering that you can reduce the HTML document sizes to one third, presumably you will pay for the fraction of the necessary original bandwidth.

What's the purpose of the anti profanity engine for IIS?
It's an experimental project, which wants to target websites with children's audience. We offer a filter of "bad words" defined in a dictionary to enhance the education and protection of the youngest internet users.

How can these products be so great and so cheap?
The prices are fair. We invest less than our competitors in GUI interactive installation/removal or other interactive procedures, that consume time of development, thus money. Our efforts target the implementation of the code, using the RTL framework in development. The quality of the SmartIIS algorithms is absolutely excellent.

Aren't you aware of piracy? How can I get support?
The problem of the shareware model is the ever growing piracy. A software author has two choices: either he can try to build a traditional company by selling a product at high price with hardware lock keys or similar methods, or he can adopt a shareware model, hoping that a large number of sold licenses can answer the problem of piracy. For this software we have chosen the shareware startup, the support is done by a open forum community with the author's answers. Considering the fair price, if you like this software and wish to use it in your production servers, please license it. Thank you.

Can I trust the benchmark results?
Indeed, this is a good question. Business fairness and honesty are our core values. We never do any unfair marketing against our competitors. We only advertise the true facts. For this purposes you can download a benchmark with open source code (Delphi 2006), and test it by yourself. Please use a TCP grabber to see if the other product provides compressed output; then, if so, please run a benchmark and report us the results: if you find different results than we did, we will update or remove immediately our speedup claims with sincere apologies to the whole community.

How does CompressContent perform on modern multiCPU systems?
The scalability of our RTL engine is exceptional, and it allows to optimize dynamically upon the back CPU architecture. You can use it also over 32-way systems, this software parallelizes all the requests linearly and without contentions or global locks.

Can you explain how can you compress documents with code?
Please take a look at the schema below. You have a webserver that receives a request from an internet browser (eg. www.smartiis.com); usually your webserver takes the file from the disk and sends it to the remote user's browser. In case of dynamic content, the webserver forwards the request to a backend engine (e.g. ASP.NET) that processes the request and provides an output. SmartIIS Compress Content takes this output before it's sent to the net, checks if it can be compressed, and if so, it compresses the content. The final user will receive exactly the same document, but within less time and consuming less bandwidth.

A simple diagram of Compress Content filter.

Does the compression filter work only with dynamic webpages?
By default, yes. If you also want to compress static pages, please contact us and we will send you a library that compresses also plain static files. Based on our benchmark results, indeed we are still 300% faster than some competitors, who also serve static files. They use a cache lookup, but our engine is so fast, that it beats them doing it in realtime. IIS4, IIS5 come with poor and unreliable support for compressed files, so our library fits the requirements perfectly. A good case scenario with IIS6 can use it for static files, and our Compress Content is excellent on dynamic pipelined pages. In case of large custom request, we will add also a cache lookup for static files compression support.

Does the compression filter work with every framework?
A webserver extension can be built in two ways: the first is to build an ISAPI filter, the second is to build an Http Handler or Http Module. ISAPI filters act inside the webserver application space and provide maximal performance, but they compromise the reliability of the server, and require low level skills to avoid. In contrast, Http Handlers and Modules are built using managed code, which is slower than native code, but easier to create and manage. Our software acts as ISAPI filter, processing all the requests of the other ISAPI filters. For example ASP.NET has ISAPI filter, so CompressContent post-process .aspx documents. Other extensions permitted by our filter are asp, aspx, php, jsp, and coldfusion (note that easily we can add other extensions upon request).

Can the compression filter shrink images dinamically?
No, with the actual hardware it's impossible, but if we get reliable results, then the next version of CompressContent will provide an ultra fast lookup cache, with reduced image size for 56K modem users.