Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 12455 invoked from network); 20 Jul 1999 15:35:11 -0000 Received: from unknown (HELO mytown.us.world.net) (209.162.210.179) by apache.org with SMTP; 20 Jul 1999 15:35:11 -0000 Received: from mytownnet.com ([206.103.58.95]) by mytown.us.world.net (Netscape Messaging Server 3.01) with ESMTP id AAA10824 for ; Tue, 20 Jul 1999 08:37:47 -0700 Sender: "Craig McClanahan" Message-ID: <3794977D.59A7CA42@mytownnet.com> Date: Tue, 20 Jul 1999 15:36:29 +0000 From: "Craig R. McClanahan" Organization: MyTown Network, Incorporated X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: request for review: server/config discussion References: <3792E4C6.490C98D6@eng.sun.com> <37934C0F.9A3C14B8@mytownnet.com> <37939183.19BEEFA1@eng.sun.com> <3793CFC6.1B106C26@mytownnet.com> <37944BF1.4EF6779@algroup.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ben Laurie wrote: > "Craig R. McClanahan" wrote: > > My single biggest gripe about Apache (or Netscape Enterprise Server, and I'm sure lots of others), > > no matter now good it is at what it does, is the fact that you have to restart the server for the > > most trivial configuration file changes. To me, that's not the way things should work -- it should > > be possible to make incremental changes to existing configurations, at least to some level, without > > global restart being required. This doesn't seem to be a high priority for most server > > developers (and I'm talking to myself here as well -- Apache JServ 1.1-DEV still requires restarts > > on config changes), but it sure does matter in environments where a server restart can be very > > disruptive to lots of users. > > a) Apache supports "graceful" restarts for this reason. The Apache source code is pretty dense, but it looks like a graceful restart still kills all the child httpd processes and recreates them. Among other things, that seems to mean all the modules go through their initialization lifecycle again. > > b) Supporting incremental changes could get pretty complicated, because > of cached derived information. I suppose simply blowing away all the > caches is feasible, though. > Speaking as an author of server-side stuff as well (Apache JServ 1.1-DEV) I am familiar with the "pretty complicated" parts of it. Basically, you can no longer count on certain things being static for the life of your server, and this has lots of ramifications. But exit/restart is still the lazy way out of dealing with the issue. > > Cheers, > > Ben. > Craig > > -- > http://www.apache-ssl.org/ben.html > > "My grandfather once told me that there are two kinds of people: those > who work and those who take the credit. He told me to try to be in the > first group; there was less competition there." > - Indira Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org