httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@worldgate.com>
Subject Re: zdnet internet computing review
Date Fri, 17 Apr 1998 03:34:05 GMT
Hmm.  And the full review in this is:

http://www.zdnet.com/products/content/zdim/0305/299066.html

I must have missed the link from somewhere?

You know, I really hate pathetic sites that use broken applets 
on their pages for advertising that suck all the damn CPU and make
Netscape almost freeze.  It just took 5 minutes to pop up the 
preferences dialog to disable applets.  Grr!

I especially like "Administrators can sleep at night knowing that
any problem they have with Apache is their fault and is not caused
by a Web server on the rampage."

Some other interesting quotes:


   
   Ask Apache users what they like about Apache and they'll tell you it's
   the complete control they have over their Websites. Sure, there are a
   lot of servers out there with great interfaces, packed with features,
   but it's impossible to tell exactly what's going on behind the scenes.
   
   With Apache you get access to the source code and thus full control of
   the server. For example, by placing "directives" or commands in
   Apache's core configuration file, httpd.conf, we could control user
   access, define document paths, set Common Gateway Interface (CGI)
   variables and define virtual hosts. While this method may not be
   intuitive, users are aided with manuals, an excellent discussion forum
   through Usenet, and a Website with an extensive set of FAQs and bug
   fixes. Administrators can sleep at night knowing that any problem they
   have with Apache is their fault and is not caused by a Web server on
   the rampage.
   
   But one little configuration file does not Apache make. Add-on modules
   make Apache the most extensible Web server on the market. Many modules
   are included with the Apache source code and we could pick and choose
   which ones to compile. But users can also create their own modules or
   pull them down from Apache's Website to integrate them with their
   existing server without sacrificing the server's integrity. This
   approach integrates well with the various versions of Unix and is
   similar to IIS/NT 4.0 model in which the Web server sits on top of the
   NT operating system and a collection of snap-in server components can
   be added or subtracted.
   
   Now that you know that Apache is highly configurable and extensible,
   if you're willing to wrestle with the command line interface, you
   should go out and get it, right? After all, it is free. Not so fast.
   Apache comes with only basic Web page authoring tools, no content
   management tools, a limited search engine, and no built-in SSL support
   (although you can download a free SSL module from Apache, which you
   can only use on noncommercial Websites.) To get the extra features you
   may need for a commercial site, you have to purchase third-party tools
   or download freeware components that may deliver subpar performance.
   There is also a commercial version of Apache, called Stronghold
   (http://stronghold.ukweb.com), which offers SSL 2.0 and 3.0 support
   for commercial applications along with technical support, but again
   that's for a fee.
   
   But don't think that Apache leaves you out in the cold. It comes with
   an FTP server, an NNTP server for newsgroups and Internet Message
   Access Protocol 4 (IMAP4) and Post Office Protocol 3 (POP 3) servers
   for e-mail. It also provides strong access controls and an excellent
   application development environment. Using the Apache API, developers
   can write their own modules and can also use ODBC to connect to any
   ODBC-compliant database.
   
   There are also various modules available for other types of database
   connectivity. Through the Java-Apache project (http://
   java.apache.org), users can download an add-on to connect to databases
   via Java Database Connectivity (JDBC), as well as integrate Java code
   and support for Java servlets into their applications. Apache is for
   users who want control, stability, and extensibility as well as those
   who are more comfortable working with the command line and files than
   mouse clicks and pretty pictures.


Mime
View raw message