Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <A5374D237E78D41195810090279CC91A05602E4B@xcup04.cup.hp.com>
From: "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)"
 <madhusudan_mathihalli@hp.com>
To: "'dev@httpd.apache.org'" <dev@httpd.apache.org>
Subject: RE: ssl_var_lookup()...
Date: Mon, 5 Nov 2001 17:31:25 -0800 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

That's true. ssl_var_lookup() is really bad in terms of performance (a hash
table is probably better).. If you're looking out for only a couple of
parameters, it's rather efficient to lookup those variables directly..

-Madhu

-----Original Message-----
From: Doug MacEachern [mailto:dougm@covalent.net]
Sent: Monday, November 05, 2001 4:44 PM
To: dev@httpd.apache.org
Subject: Re: ssl_var_lookup()...


On Mon, 5 Nov 2001, Bill Stoddard wrote:

> I have a module that needs access to SSLCIPHER, SSL_CLIENT_CERT and
SSL_SESSIONID. What is
> the right way for a module to get at this info?  I see a couple of
methods:
> 
> 1. Use SSL_* calls directly
> 
> 2. Call ssl_var_lookup()
>     This call looks to be very inefficient. Full of string compares. And
the call is not
> exported for use on Windows either (which is easy enough to change).

it is registered as an optional function.  for an example see:
httpd-test/perl-framework/c-modules/test_ssl/mod_test_ssl.c

as for performance of ssl_var_lookup(), that certainly should be improved.