On Wed, Mar 17, 2010 at 8:15 AM, Noirin Shirley <[email protected]> wrote: > On Wed, Mar 17, 2010 at 12:37 PM, Rich Bowen <[email protected]> wrote: >> Summary: >> >> It appears that the majority is in favor of 'Apache HTTP Server' when >> referred to in full, but there doesn't seem to be much of a consensus of how >> this should be abbreviated, so that we don't have to say the full name every >> time. > > Looking at the example sentences below, it seems to me that "Apache > HTTP Server" and "the server" could be the solution to all of this.
Yes; this will be the readable solution in many instances. (I think Dan suggested something like this -- maybe "the web server" -- in a different thread.) > >> In deciding what file to serve for a given request, the server's >> default behavior is to take the URL-Path for the request (the part >> of the URL following the hostname and port) and add it to the end >> of the <directive module="core">DocumentRoot</directive> specified >> in your configuration files. >> >> >> Apache HTTP Server is also capable of <a href="vhosts/">Virtual >> Hosting</a>, where the server receives requests for more than one >> host. >> >> Apache HTTP Server offers several different ways to accomplish this. >> > > The last is mildly clunky, but I don't think there's a completely > clunk-free option on the table anyway. > > N -- Born in Roswell... married an alien... --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
