httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noirin Shirley <noi...@apache.org>
Subject Re: Suexec doc (Was Re: Fixing confusion of Apache vs httpd)
Date Sat, 13 Mar 2010 18:13:56 GMT
On Sat, Mar 13, 2010 at 7:01 PM, Rich Bowen <rbowen@rcbowen.com> wrote:
>
> If we're going to do a massive sed, my preference would be for Apache
> HTTPD and HTTPD, because the capitalisation avoids the confusion
> between httpd-the-server and httpd-the-command, and it's fewer words
> :-)
>
> Going that way also means you don't have to worry about including the
> short form in parentheses after the first reference - it's easy to
> intuit that "HTTPD" and "Apache HTTPD" mean the same thing, whereas
> it's less obvious what the connection is between "httpd" and "Apache
> HTTP Server".
>
> If we're going with Apache HTTP Server and httpd, I think it's
> important to *avoid* markup when we mean the webserver, and to
> (consistently, if we can!) *use* markup when we mean the command.
>
>
> Hmm. I didn't think we had a choice in what name we used. I figured that was
> a question of trademark.

>From my understanding, there's no trademark-based reason that Apache
HTTP Server is better than Apache HTTPD. We've used both, fairly
interchangeably, to refer to the same thing for a long time.

That doesn't mean my way is the right way, just that we should worry
about docs and code, and let lawyers worry about the other stuff :-)

Larry, can you confirm?

N

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Mime
View raw message