Re: caching dynamic pages

> Correct me if I'm wrong, but you want tux to work as a proxy in
> reverse mode? 

Correct!

> If that is so, I'm not sure tux can do that.

The documentation gives me the impression Tux can do this:

The tux.README says:
   But dynamic content is becoming a larger and larger part of the
   web, and TUX provides a way to cache dynamic content as well.

And http://www.redhat.com/docs/manuals/tux/TUX-2.2-Manual/intro.html
says: "Red Hat Content Accelerator also has the ability to cache dynamic
content." 

But it is not clear to me how this can be achieved. 

The same page also says "....can create "objects" which are stored using
the page cache". I don't hope this means that the complete cache will be
kept in memory...


> An alternative would be the following:
> 1. Configure tux as the main web server to serve static content.
> 2. Configure squid as a reverse proxy and use it as the clientport.
> 3. Have squid forward requests to apache (on another port) and apache
>    set the right cache control headers so squid can do the right
>    caching.

Actually we have set up caching with apache already. There is a
front-end "light weight" httpd (with mod_proxy)  which serves static
pages, act as proxy for dynamic pages and caches the dynamic pages. At
the back-end there is a heavy weight httpd with mod_perl.

This works relatively well. The point is, I am not happy with mod_proxy.
It's garbage collection (cleaning the cache) unusable, because it causes
periodically (when it starts cleaning) a serious I/O bottleneck. (I made
a shell script with sleep and tmpwatch commands to do the job). 

Regarding caching, Squid could do a better job maybe, but would
introduce a more heavy weighted solution.

Tux seems to be an ideal alternative, because it is designed for this
kind of situations (at least, I think it is).