Mark Bixby writes,

> The NCSA web server port is seriously out of date and uses a
> poorly performing
> "fork each request" architecture.

Or in laymen's terms, as I wrote to the writer privately:

"Depending on the load on the machine, you will find that the NCSA port can
be sluggish.  It is a single-threaded model and as such, on a heavily used
machine or on an ill-configured machine (especially memory), it will slow
down - a lot.

"Also, if it's being hit with a lot of requests, you will find that because
of its single-threaded model, each requests queues up and waits its turn.
In other words, there is no pool of server process threads waiting on
requests, like there is in Apache or in the upcoming Netscape FastTrack
server, as well as in the NT-based servers."

Means the same thing :) Fork each request --- single-threaded... tomato,
tomahto :)

> I encourage you to upgrade to Apache/iX, which has a better
> server pool
> architecture and should be upward compatible with the NCSA server:
>

I wholeheartedly agree --- The NCSA server is great to cut ones teeth on or
to use as a server which will not be performing a great deal of work... for
industrial strength, look at Apache, and/or the upcoming Netscape FastTrack
server.

For MPE-Centric folks (or shall we say, those who stay away from Posix),
there's also QWEBS from QSS (and I think we already heard Duane chime in
earlier :)

Best Regards,
Joe

==========================================================
Joe Geiser, Senior Partner, CSI Business Solutions, LLC
 ** Your Client-Server and Internetworking Specialists **
Phone: +1 (215) 945.8100  Fax: +1 (215) 943.8408
*New* Toll-Free (US/Canada): (877) 945-8100
http://www.csillc.com      mailto:[log in to unmask]
==========================================================
HP Channel Partner         Allaire Alliance Partner
Microsoft ClubWin - Team One