Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of margol@beamartyr.net
 designates 199.203.54.245 as permitted sender)
Message-ID: <4AEFE0D1.2000209@beamartyr.net>
Date: Tue, 03 Nov 2009 09:50:41 +0200
From: Issac Goldstand <margol@beamartyr.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: dev@httpd.apache.org
CC: modules-dev@httpd.apache.org
Subject: Re: Visiting mod_authn_cache
References: <4AED52C4.5050609@beamartyr.net> <4AEEA324.4010206@beamartyr.net>
 <4AEEA790.6000501@sharp.fm> <4AEEBB46.1020703@beamartyr.net>
 <4AEEC004.1090803@sharp.fm>
In-Reply-To: <4AEEC004.1090803@sharp.fm>
OpenPGP: url=http://www.beamartyr.net/pubkey.asc
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit

Graham Leggett wrote:
> Issac Goldstand wrote:
>
>   
I actually ended up solving it with the help of socache's source.  I was
having troubles with apr_time_t's and saw that socache uses plain 'ol
time_t.  After switching, everything just worked.  So technically, I'm
done.  (I'd be happy to submit the jumbo-patch to mod-auth, not sure if
work will leave me time to start seperating it into chunks)
>> Nope, it's not what I was using.  I wanted to keep it 2.2.x compatible
>> since I need this module in production, although I completely agree with
>> the point.
>>     
>
> We also use socache in v2.2, and to solve that problem, I backported the
> socache modules as external modules. Not all the socache modules build
> cleanly, but the key ones we needed did.
>   
Can you tell me what worked?  If the shared memory cache works, I may
get some extra time at work to rewrite for socache, just so that all of
the children can use a single cache, instead of one per child.

Also, any pointers to sample code for socache would be nice.  I *think*
I get how it's supposed to be used, but a concrete example would save
some time.

  Issac