Web Booster
Makes web applications faster and more reliable
Web Booster reduces the load on your existing HTTP infrastructure by caching commonly used web content. It also dynamically gzips web content, vastly improving network transfer speeds. No complicated network infrastructure is required and no software needs to be installed on workstations.
Tuned for Lotus Domino
Web Booster is tuned to work with Lotus Domino (but works fine with all HTTP servers). Domino can produce a lot of dynamic html, especially when browsing "views" of documents, by adding Web Booster to your Domino environment the html is reduced to a fraction of its original size. In most cases 10% to 30% of its original size! Admins love Web Booster because its dynamic failover means that if a Domino server crashes or needs to be restarted in the middle of the day, requests are automatically routed to nodes that are available, without any user impact.
Web Booster is perfect for a Lotus Domino Web Mail cluster. It evenly spreads the user load across the mail cluster and provides a higher availability of your mail service. When your users connect to their mail using a slow dialup or mobile connection, Web Booster's compression routines allow them to work as if they were in the office.
Get the presentationYour existing infrastructure, just faster!
Adding Web Booster to your environment allows you to use all your existing servers, with Booster making them run faster and more reliably. Web Booster is a server-side technology so there is no workstation software rollout or reconfiguration, just slot it in and turn it on. Take a look now at how it can speed up your servers using our realtime URL report
Sounds too good to be true. How does it work?
Web requests are intercepted by Web Booster. If Booster can satisfy the request itself it does, serving content from its cache. Other requests are passed to the backend HTTP servers, processed and returned to Booster. Web Booster then determines if the client can accept compressed content and if the content from the backend server may be compressed. If the content may be compressed, it is gzipped then a much smaller reply is sent back to the browser. See the following example comparing a traditional HTTP server with one accelerated using Web Booster.