Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <200508172129.j7HLT7v14466@devsys.jaguNET.com>
Subject: Re: [PATCH] mod_disk_cache deterministic tempfiles
To: dev@httpd.apache.org
Date: Wed, 17 Aug 2005 17:29:03 -0400 (EDT)
Reply-To: jim@jaguNET.com
In-Reply-To: <20050817205232.GA2898@stdlib.net> from "Colm MacCarthaigh" at
 Aug 17, 2005 09:52:32 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Colm MacCarthaigh wrote:
> 
> On Wed, Aug 17, 2005 at 04:11:01PM -0400, Brian Akins wrote:
> > I have the thought that we could also serve files that have "recently 
> > expired" (recent being configurable) if the object was being cached. 
> > Psudocode:
> > 
> > if(expired < (now - recent)) {
> 
> Content definitely should not be served from the cache after it has
> expired imo. However I think an approach like;
> 
>     if((now + interval) > expired) {
>         if(!stat(tmpfile)) {
> 	    update_cache_from_backend();
> 	}
>     } 
> 
> ie "revalidate the cache content after N-seconds before it is due to be
> expired" would have the same effect, but avoid serving stale content.
> 

Would be interesting to profile that to determine how expensive those
stats could be...

-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
                     "Sith happens"  -  Yoda