Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of margol@beamartyr.net designates
 199.203.54.245 as permitted sender)
Message-ID: <4C19D06C.1030808@beamartyr.net>
Date: Thu, 17 Jun 2010 10:36:12 +0300
From: Issac Goldstand <margol@beamartyr.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: mod_authn_cache
References: <20100616232934.300087a4@baldur>
In-Reply-To: <20100616232934.300087a4@baldur>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I think I sent a patch to fix it up a year or so ago, when I needed it 
for 2.2.  You can see the fully working (live in production for 6 months 
now, I think) code here.
http://sourceforge.net/tracker/download.php?group_id=93106&atid=603134&file_id=350405&aid=2895850

As mentioned there, I wanted this to work against 2.2, but for trunk I'd 
have probably used socache instead of the static array used here.

   Issac

On 6/17/2010 1:29 AM, Nick Kew wrote:
> I thought we had a mod_authn_cache, but it seems it only exists in the
> old 2.1 authn stuff at sourceforge!
>
> Just thinking about hacking this up, and wondering how best to do it.
> Basic shape seems straightforward enough:
>
> 1.  Make it a provider like the standard mod_authn_****
> 2.  Configure it ahead of anything heavyweight like dbd.
> 3.  Export an optional function for other mod_authn_* modules to cache
>      credentials they've looked up.
> 4.  Timestamp everything in cache, and provide a configurable timeout.
>
> But how to implement the cache itself is less clear.  The simplest solution
> would be to hijack mod_authn_dbm and add a cacheing function and configuration.
> But the new socache framework presents an alternative, and an option for users
> of threaded MPMs to run a per-process cache would add value.
>
> Thoughts?
>
>