Message-ID: <3474B806.B4A1D873@prairie.nodak.edu>
Date: Thu, 20 Nov 1997 16:21:58 -0600
From: Igor Tatarinov <tatarino@prairie.NoDak.edu>
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: Want to add file caching to Apache
References: <Pine.NEB.3.96.971120213523.9334A-100000@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Rob Hartill wrote:
> 
> 
> serving static content is pretty trivial and has almost no overhead
> on reasonable hardware.
> 
> I've got a 586 Pentium 166mhz doing >20 static file requests per second
> with 90% idle cpu and a load of ~0.2 . It also acts as a mailing list
> server and nameserver when it gets bored.
> 
> I'm not knocking the idea of caching but do wonder if it's a solution
> to a relatively unimportant problem. Are there better bottlenecks to
> take a shot at widening ?

A related question: is it possible to cache cgi script output?
I've heard that SQUID guys check for ? in the file name to find out
if the file was produced by a cgi script. Of course, they also check
the response header but it's not always setup correctly. Anyways, 
sometimes they may cache cgi scripts.

It is probably impossible to cache POST reponses but with GETs there 
should be no problem. 

igor