Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 62005 invoked from network); 3 May 2006 18:37:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 May 2006 18:37:33 -0000 Received: (qmail 51890 invoked by uid 500); 3 May 2006 18:37:29 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 51828 invoked by uid 500); 3 May 2006 18:37:28 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 51817 invoked by uid 99); 3 May 2006 18:37:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2006 11:37:28 -0700 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of gonzalo.arana@gmail.com designates 64.233.166.176 as permitted sender) Received: from [64.233.166.176] (HELO py-out-1112.google.com) (64.233.166.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2006 11:37:27 -0700 Received: by py-out-1112.google.com with SMTP id d80so281031pyd for ; Wed, 03 May 2006 11:37:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RAhXL/v0f0wbMj1OF0Ne1LT/dHGO8ZEexRym/bTXNtuloIjhO2/bB5r8/4XqeGFtvvKqAmf6lh+b5eKBDXL/ics0ios0js6ktwfb4dN+odFY6vgWX1rc/RFhLWlvNZXD5tUe1mNQpiBXYWYRn0nQvjYD/9qq4u/75hYCSEJW0j0= Received: by 10.35.127.7 with SMTP id e7mr1239080pyn; Wed, 03 May 2006 11:37:06 -0700 (PDT) Received: by 10.35.62.7 with HTTP; Wed, 3 May 2006 11:37:06 -0700 (PDT) Message-ID: Date: Wed, 3 May 2006 15:37:06 -0300 From: "Gonzalo Arana" To: dev@httpd.apache.org Subject: Re: Possible new cache architecture In-Reply-To: <4458F0DD.6030000@sharp.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4450CF63.2060305@turner.com> <11424.196.8.104.37.1146583320.squirrel@www.sharp.fm> <20060502153543.51f13082.davi@haxent.com.br> <4457CFA1.9040908@sharp.fm> <20060502195439.db25863b.davi@haxent.com.br> <4457E68F.2050801@sharp.fm> <20060502202633.2c1e11b3.davi@haxent.com.br> <27345.196.8.104.37.1146659466.squirrel@www.sharp.fm> <4458EC5A.3030405@turner.com> <4458F0DD.6030000@sharp.fm> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Excuse my ignorance in this matter, but about the 'cache sub-key' issue, why not just use a generic cache (with some expiration model -LRU, perhaps-) with a 'smart' comparison function? We could use as key full request headers (perhaps somewhat parsed), and as a comparison function a clever enough code to handle Vary, entity aging and so on. Best regards, -- Gonzalo A. Arana