Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Subject: Re: Letting Table store non-char data
From: Ian Holsman <IanH@cnet.com>
To: dev@httpd.apache.org
In-Reply-To: <3B843505.9020503@pacbell.net>
References: <998514781.12703.10.camel@c1619481-a.almda1.sfba.home.com>
	<01082214120501.18802@koj.rkbloom.net>
	<998515720.12703.17.camel@c1619481-a.almda1.sfba.home.com>
	<3B843505.9020503@pacbell.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 22 Aug 2001 15:59:56 -0700
Message-Id: <998521196.12699.55.camel@c1619481-a.almda1.sfba.home.com>
Mime-Version: 1.0
Status: O

On Wed, 2001-08-22 at 15:41, Brian Pane wrote:
> Ian Holsman wrote:
> 
> >On Wed, 2001-08-22 at 14:12, Ryan Bloom wrote:
> >
> >>We had binary tables, but we removed them, because that is what hash
> >>tables are for.
> >>
> >agreed.
> >but there are no hash tables on the request rec structure.
> >
> >My problem is that I have a module which implements a custom SSI tag and
> >a 'postfix' hook.
> >the postfix hook sets up the key based on the incoming request.
> >
> >when the SSI tag gets called (~10-50 per page) it needs to get the key 
> >the postfix hook had set up.
> >
> >another module we have does a lot of work in the SSI call and needs to
> >cache the data for subsequent calls to itself.
> >
> How about changing request_rec->notes to a hash table?  This would be
> a relatively simple change, as the notes field isn't used in a huge
> number of places in the standard modules.
> 
> --Brian
> 
that would work for me.
I could submit a patch tonight to do this.
> 
-- 
Ian Holsman
Performance Measurement & Analysis
CNET Networks    -    415 364-8608