To: new-httpd@apache.org
Path: dgaudet
From: dgaudet@hotwired.com (Dean Gaudet)
Newsgroups: hot.mailing-lists.new-httpd
Subject: Re: BrowserMatch concerns
Date: 26 Sep 1996 09:59:38 GMT
Organization: HotWired Ventures
Lines: 36
Message-ID: <52dk6a$g2i@re.hotwired.com>
References: <199609251753.NAA12019@telebase.com.>
 <hot.mailing-lists.new-httpd-Pine.SGI.3.93.960925202409.22994k-100000@fully.organic.com>
NNTP-Posting-Host: get.wired.com
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

Just an idle thought... there's no protection against name clashes in
configuration directives.

Dean

In article <hot.mailing-lists.new-httpd-Pine.SGI.3.93.960925202409.22994k-100000@fully.organic.com>,
Brian Behlendorf  <new-httpd@hyperreal.com> wrote:
>On Wed, 25 Sep 1996, Chuck Murcko wrote:
>> Ben Laurie liltingly intones:
>> > 
>> > Two points, one of which I have mentioned before, with no clear consensus.
>> > 
>> > 1. BrowserNoCase is puzzlingly named - I think it should be more strongly
>> > reminiscent of BrowserMatch - BrowserMatchNC or BrowserMatchNoCase, for
>> > example.
>
>Yeah, I agree, BrowserMatchNC is probably just cleaner.
>
>> > 2. We use BrowserMatch variables internally (cf. nokeepalive), but have not
>> > guarded against name collisions. I propose that we reserve some kind of prefix
>> > for internal use. I suggested '-' last time, but for some reason people didn't
>> > like it. How about '+'?
>> > 
>> Oh, that. +,-,_, it all works for me. + connotes turning something on, I
>> would think, whereas - might mean turning it off (except to *nix folks).
>
>The variable names need to be easy to access from other languages, in my
>opinion.  I'd prefer "ap_" over anything else.  
>
>	Brian
>
>--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
>brian@organic.com  www.apache.org  hyperreal.com  http://www.organic.com/JOBS
>