Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of wrowe@rowe-clan.net
 designates 209.85.213.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <552F3D9C.7010401@velox.ch>
References: <20150415163613.GC15209@fintan.stsp.name>
	<552F3D9C.7010401@velox.ch>
Date: Thu, 16 Apr 2015 14:57:20 -0500
Message-ID: 
 <CACsi250EZqUxFgqr+rb1mZcQCBk62bqRRcjLN1AbFiN+UTjy-A@mail.gmail.com>
Subject: Re: namespacing in mod_ssl
From: William A Rowe Jr <wrowe@rowe-clan.net>
To: dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=047d7bea429417e20e0513dcdf09

--047d7bea429417e20e0513dcdf09
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 11:42 PM, Kaspar Brand <httpd-dev.2014@velox.ch>
wrote:

> On 15.04.2015 18:36, Stefan Sperling wrote:
> > However, the actual issue here is that mod_ssl is squatting the SSL_
> namespace.
> > Historically this may have made sense (it seems mod_ssl and OpenSSL have
> > shared history/authors). Bill Rowe suggested to try moving mod_ssl's
> > functions into the ap_ namespace to avoid such clashes in the future.
>
> Agreed that mod_ssl should avoid stepping into the SSL_* yard. As
> pointed out by Jeff, ap_* is fairly foreign in the mod_ssl case, though,
> and my preference is for s/SSL_/ssl_/ for functions and
> s/SSL_/MODSSL_/ for constants (in the latter case, there's actually
> quite some more stuff lurking - SSL_OPT_*, SSL_PROTOCOL_* etc.).
>

+1

--047d7bea429417e20e0513dcdf09
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 11:42 PM, Kaspar Brand <span dir=3D"ltr">&lt;<a href=3D=
"mailto:httpd-dev.2014@velox.ch" target=3D"_blank">httpd-dev.2014@velox.ch<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On=
 15.04.2015 18:36, Stefan Sperling wrote:<br>
&gt; However, the actual issue here is that mod_ssl is squatting the SSL_ n=
amespace.<br>
&gt; Historically this may have made sense (it seems mod_ssl and OpenSSL ha=
ve<br>
&gt; shared history/authors). Bill Rowe suggested to try moving mod_ssl&#39=
;s<br>
&gt; functions into the ap_ namespace to avoid such clashes in the future.<=
br>
<br>
</span>Agreed that mod_ssl should avoid stepping into the SSL_* yard. As<br=
>
pointed out by Jeff, ap_* is fairly foreign in the mod_ssl case, though,<br=
>
and my preference is for s/SSL_/ssl_/ for functions and<br>
s/SSL_/MODSSL_/ for constants (in the latter case, there&#39;s actually<br>
quite some more stuff lurking - SSL_OPT_*, SSL_PROTOCOL_* etc.).<br></block=
quote><div><br></div><div>+1=C2=A0</div></div><br></div></div>

--047d7bea429417e20e0513dcdf09--