I still stand by Apache Server Framework as the best choice.
I like this a lot too!
(Or either Apache World Dominitation Project j/k)
--
~Jorge
William A. Rowe, Jr. wrote:
Colm MacCarthaigh wrote:
On Thu, Aug 10, 2006 at 12:26:23PM -0700, William A. Rowe, Jr. wrote:
Pretty darned quiet - either it's summer or nobody feels like
joining the fray when Roy and Will go at it?
Well, Paul's talk in San Diego got me thinking. We're not
Paul Querna wrote:
I still stand by Apache Server Framework as the best choice. The ASF'S
ASF is the ultimate way to deliver data from a server :)
:) ++1
* Jim Jagielski wrote:
Apache HTTP Server is (mostly) a web server.
Let's call it 'parker'
Good call.
Did you know, that 'nd' is short for
n.d. parker
:-)
Roy T. Fielding wrote:
I agree, though if we change it we may as well go to apache-server-2.4.x
given the noise about protocol-independence.
+1 and I've changed -this- thread subject to discuss what the name is right now.
Only recently did people start changing the text to remove httpd,
Roy T. Fielding wrote:
People discuss what to put in the Announcement text on every release,
but the only discussion I've seen about our product name was Paul's
suggestion we change it to d.
yeah, that was funny :)
--
Roy T. Fielding wrote:
It is the name of the product containing a whole bunch of source code
and many binaries, one of which is sometimes called httpd. The tarballs
are called httpd. The legal notices will be called httpd, and the links
to the artifacts will be called httpd. The only
On Jul 28, 2006, at 12:32 PM, William A. Rowe, Jr. wrote:
From this perspective and for clarity, while we are on the subject,
perhaps
apache-httpd-X would be the appropriate package names, and
seems that
would be consistent with how most many ASF projects are
distributing their
tarballs
On Friday 28 July 2006 19:51, Roy T. Fielding wrote:
Our product is
apache_1.3.37.tar.gz
httpd-2.0.59-win32-src.zip
httpd-2.0.59.tar.gz
httpd-2.2.3-win32-src.zip
httpd-2.2.3.tar.gz
and the NOTICE files are tied to the source tree (httpd).
Isn't the whole problem
Let me sugest:
:: Nahche ::
Nahche (Na-ai-che, `mischievous,' `meddlesome.'-George Wrattan). An
Apache warrior, a member of the Chiricahua band. He is the second son
of the celebrated Cochise, and as hereditary chief succeeded his elder
brother, Tazi, on the death of the latter. His mother was a
On Friday 28 July 2006 22:59, Jorge Schrauwen wrote:
Let me sugest:
:: Nahche ::
Nahche (Na-ai-che, `mischievous,' `meddlesome.'-George Wrattan). An
Apache warrior, a member of the Chiricahua band. He is the second son
of the celebrated Cochise, and as hereditary chief succeeded his elder
Nick Kew wrote:
Isn't the whole problem the lack of a proper product name that
we or anyone can identify with (other than Apache)?
With that in mind, how about something more distinctive and
less ineffably lame than anything like httpd or web server?
For example, draw on our heritage and
I wouldn't push the "Apache" thing.
Truth is... a letter could show up at any moment from lawyers
of the Apache Nation regarding the name usage.
Might even be way overdue.
I wouldn't "go there" and draw attention to the issue at all.
Yours...
Kevin Kiley
In a message dated 7/28/2006
Jorge Schrauwen wrote:
Let me sugest:
:: Nahche ::
Nahche (Na-ai-che, `mischievous,' `meddlesome.'-George Wrattan). An
Apache warrior, a member of the Chiricahua band. He is the second son
of the celebrated Cochise, and as hereditary chief succeeded his elder
brother, Tazi, on the death of
Fair point you have there...
As long as the new name isn't some way to hard to rememebr abrivation :)
AMPES ;) Apache Multi Protocal Extenable Sever j/k
On 7/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I wouldn't push the Apache thing.
Truth is... a letter could show up at any
Apache HTTP Server is (mostly) a web server.
Let's call it 'parker'
(I'll let the Spider Man fans explain it... :) )
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
If you can
16 matches
Mail list logo
