You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Dean Gaudet <dg...@arctic.org> on 1997/07/14 06:52:51 UTC

praise

---------- Forwarded message ----------
Date: Sun, 13 Jul 1997 21:04:01 -0700 (PDT)
From: Morgan Davis <md...@freek.cts.com>
To: Dean Gaudet <dg...@arctic.org>
Subject: Re: config/861: NCSA Compatibility with VirtualHost

Dean Gaudet writes:
> The response time does depend on how busy each of us is ... naturally. 
> The easy PRs usually get quick responses :) 
> 
> Mind if I forward this to the rest of the development group?
> 
> Thanks
> Dean

Go right ahead.  I know it's not a one-man show, so please spread the
thanks around.  I'm looking forward to working with you guys and hope
I can contribute in constructive ways to help make Apache even better.

--Morgan


> On Sun, 13 Jul 1997, Morgan Davis wrote:
> 
> > Dean:
> > 
> > Just a real quick word of praise on Apache and some background so you
> > know where I'm coming from.  I started out in 1993 administrating NCSA
> > servers, and until this year we continued to deploy it among our farm.
> > During that time, I had a pretty good relationship with Brandon Long
> > who was terrific in helping us resolve some real issues with NCSA that
> > affected us.  Many features of NCSA were a result of discussions with
> > Brandon on some of my ideas that we really needed.  It's good to see
> > that just about everything (and then some) is available in Apache,
> > too.  Today, we're virtually hosting about 600 sites across four NCSA
> > servers on BSDI BSD/OS.  However, from here on out, it looks like
> > FreeBSD and Apache for me.
> > 
> > I've found the transition to Apache to be painless, surprising, and
> > thrilling all at the same time.  The modular architecture for the
> > server is brilliant.  The dynamic juggling of available servers is a
> > dream.  At first glance, missing features like proctitle statistics
> > made me wonder how we'd track real-time activity.  But with continued
> > reading, learning about the status module is not just better, but
> > infinitely more useful.  (We had written tools to peek and poke at
> > NCSA in every way -- reading proctitles, counting processes,
> > monitoring interfaces via CGI, etc.  The status module gives us a
> > pretty easy way to get more info painlessly, and from anywhere).
> > 
> > I've not had more than week or so of play with Apache, but I can tell
> > already that it is likely to replace all our NCSA servers if we can
> > migrate everything over smoothly.  With 600-some commercial virtual
> > hosts (and almost as many business sites that don't have domain
> > names), we have to step carefully.  Hence my concern with some of
> > these old NCSA issues.  Most of it we can easily work around.
> > 
> > Anyhow, big thanks for excellent work, and your responsiveness.  That
> > was one of the things that I held dearly in working with NCSA.  If
> > Apache's support is as responsive and attentive as you've
> > demonstrated, I'm regretting that I had waited this long to check into
> > it.
> > 
> > Hats off.
> > 
> > --Morgan
> > 
> > Dean Gaudet writes:
> > > Ah ok, documented.
> > > 
> > > Dean
> > > 
> > > On Sun, 13 Jul 1997, Morgan Davis wrote:
> > > 
> > > > Right.  Like I said, the default behavior of Apache is just dandy,
> > > > since that's how we run/ran NCSA anyway.  But it may be worthy of a
> > > > note on the NCSA compatibility page.
> > > > 
> > > > --Morgan
> > > > 
> > > > 
> > > > Dean Gaudet writes:
> > > > > Have you read the dns-caveats.html page in the docs?  It goes over how to
> > > > > ensure things will work.  Before 1.2 it would fail if any of the dns
> > > > > lookups failed, and we had many complaints about that, hence we downgraded
> > > > > it to just a warning.  The NCSA syntax would mean we'd get those
> > > > > complaints all over again since few users bother reading any
> > > > > documentation.  And the syntax is incompatible with apache because we
> > > > > allow multiple names/ips on the <VirtualHost> line. 
> > > > > 
> > > > > A site concerned that things are really working right would also need a
> > > > > monitoring setup to monitor their httpd ... and that would make the need
> > > > > for this feature kinda questionable.
> > > > > 
> > > > > Dean
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > >    ___ ____ ___
> > > >   /     /  /__   Network  |  619/637-3600 x 1020  |  mailto:mdavis@cts.com
> > > >  /__   /  ___/  Services  |  FAX 619/637-3630     |  http://www.cts.com/
> > > > 
> > > 
> > > 
> > 
> > 
> >    ___ ____ ___
> >   /     /  /__   Network  |  619/637-3600 x 1020  |  mailto:mdavis@cts.com
> >  /__   /  ___/  Services  |  FAX 619/637-3630     |  http://www.cts.com/
> > 
> 
> 


   ___ ____ ___
  /     /  /__   Network  |  619/637-3600 x 1020  |  mailto:mdavis@cts.com
 /__   /  ___/  Services  |  FAX 619/637-3630     |  http://www.cts.com/