From: sp...@indra.com (Joe Ilacqua)
Subject: NCSA 1.4 vs Apache 0.6.2
Date: 1995/05/12
Message-ID: <SPIKE.95May12113850@net.indra.com>#1/1
X-Deja-AN: 102583644
sender: sp...@indra.com (Joe Ilacqua)
organization: Indra's Net, Inc.  -- Public Access Internet.
newsgroups: comp.infosystems.www.servers.unix


Does anyone have a preference between NCSA httpd 1.4 and Apache 0.6.2?

->Spike
-- 
          Indra's Net  --  Internet Access with an Attitude
             Email: i...@indra.com  URL: http://www.indra.com
             Modem: (303) 786-7405  Voice: (303) 546-9151

From: Rob Hartill <hart...@lanl.gov>
Subject: Re: NCSA 1.4 vs Apache 0.6.2
Date: 1995/05/12
Message-ID: <3p0cmj$lrh@newshost.lanl.gov>#1/1
X-Deja-AN: 102583645
references: <SPIKE.95May12113850@net.indra.com>
content-type: text/plain; charset=us-ascii
organization: Los Alamos National Labs
x-url: news:SPIKE.95May12113850@net.indra.com
mime-version: 1.0
newsgroups: comp.infosystems.www.servers.unix
x-mailer: Mozilla 1.1N (X11; I; HP-UX A.09.05 9000/712)

sp...@indra.com (Joe Ilacqua) wrote:

>Does anyone have a preference between NCSA httpd 1.4 and Apache 0.6.2?

   NCSA 1.4    Apache 0.x
   ========    ==========
     fast     feature rich


We're working on pre-forking Apache, which will be faster than
NCSA 1.4, and will have less impact on the system load average.

The plan is to get the existing Apache code as stable as possible
before concentrating on the pre-forking version. 0.6.2 has had
a thourough test in the field, and there's a 0.6.4 waiting in the
wings to fix all the minor glitches that have been found. Hopefully,
there will be very few revisions to 0.6.x

For most sites (with ~100k hits/day or less), the speed difference
between NCSA 1.4 and Apache 0.x will not be noticeable.

Apart from speed and features, you should consider the future of the
two. NCSA's goals for httpd server developement aren't clear (to me
at least).. I suspect they will move towards prototyping and releasing
new ideas, e.g. secure http. To do that they'll have to move away from
implementing the "fluff" that the cutomers want, e.g. multi home support,
content-negotiation, dbm databases etc.

Remember, NCSA's job is to push technology - not compete with
the likes of Netsite. There will always be a need for a free httpd,
server. Apache should guarantee that.

The Apache server was created to address such issues. Apache is
a public collaborative effort, where the users determine what happens
next.

NCSA understand the role Apache aims to play in the free httpd server
market, and have been very cooperative. The NCSA httpd developers
are on the Apache developers mailing list, and lots of useful
ideas/code/bug fixes flows between the two groups.

I see both servers coexisting with their current roles for the next 6-12
months. After that ?, who knows what'll happen...


You can draw your own conclussions from all of this.


--
Rob Hartill                           
http://nqcd.lanl.gov/~hartill/

These are my own opinions... 
possibly not those of the rest of the Apache group.

From: efr...@void.ncsa.uiuc.edu (Beth Frank)
Subject: Re: NCSA 1.4 vs Apache 0.6.2
Date: 1995/05/17
Message-ID: <3pd3mv$i1v@vixen.cso.uiuc.edu>#1/1
X-Deja-AN: 102855660
references: <SPIKE.95May12113850@net.indra.com> <3p0cmj$lrh@newshost.lanl.gov>
organization: University of Illinois at Urbana
newsgroups: comp.infosystems.www.servers.unix

Rob Hartill (hart...@lanl.gov) wrote:
: sp...@indra.com (Joe Ilacqua) wrote:

: >Does anyone have a preference between NCSA httpd 1.4 and Apache 0.6.2?

:    NCSA 1.4    Apache 0.x
:    ========    ==========
:      fast     feature rich

I've got to agree with this ^

: Apart from speed and features, you should consider the future of the
: two. NCSA's goals for httpd server developement aren't clear (to me
: at least).. I suspect they will move towards prototyping and releasing
: new ideas, e.g. secure http. To do that they'll have to move away from
: implementing the "fluff" that the cutomers want, e.g. multi home support,
: content-negotiation, dbm databases etc.

Multi home support will probably make it into 1.x series (1.6 or maybe 1.5),
dbm and other database support probably won't show up until 2.x or 3.x.

: Remember, NCSA's job is to push technology - not compete with
: the likes of Netsite. There will always be a need for a free httpd,
: server. Apache should guarantee that.

: The Apache server was created to address such issues. Apache is
: a public collaborative effort, where the users determine what happens
: next.

Apache will probably always be more feature rich than the NCSA server.
We are working simulateously on the next generation server while continueing
development and support of the current server.  Right now more effort
is being put into the current server than the NG server.  A year from
now the opposite will probably be true.  One of the major goals of NCSA
is to provide technology leaps.  Focussing on bells and whistles is not
the way to do that.

: NCSA understand the role Apache aims to play in the free httpd server
: market, and have been very cooperative. The NCSA httpd developers
: are on the Apache developers mailing list, and lots of useful
: ideas/code/bug fixes flows between the two groups.

: I see both servers coexisting with their current roles for the next 6-12
: months. After that ?, who knows what'll happen...

We're hoping a year from now Apache will still be going strong.  By then
we should have our next generation stuff at least in the demo stage and
hopefully released.  Most of focus will be on the Repository ideas, and
very little, if any, new development effort will be invested in the old
server.  We're hoping new features for the old server will be addressed
by the Apache group.  We'd like our relationship to remain cooperative.

		Elizabeth Frank
		NCSA httpd Development Team
		efr...@ncsa.uiuc.edu

: --
: Rob Hartill                           
: http://nqcd.lanl.gov/~hartill/

: These are my own opinions... 
: possibly not those of the rest of the Apache group.

			  SCO's Case Against IBM

November 12, 2003 - Jed Boal from Eyewitness News KSL 5 TV provides an
overview on SCO's case against IBM. Darl McBride, SCO's president and CEO,
talks about the lawsuit's impact and attacks. Jason Holt, student and 
Linux user, talks about the benefits of code availability and the merits 
of the SCO vs IBM lawsuit. See SCO vs IBM.

Note: The materials and information included in these Web pages are not to
be used for any other purpose other than private study, research, review
or criticism.