Received: by taz.hyperreal.com (8.6.12/8.6.5) id SAA12775;
 Sun, 5 May 1996 18:31:10 -0700
Received: from krone.dialin.utoronto.ca by taz.hyperreal.com (8.6.12/8.6.5)
 with ESMTP id SAA12763; Sun, 5 May 1996 18:31:06 -0700
From: rasmus@madhaus.utcs.utoronto.ca
Received: from krone.house.mil (krone.house.mil [192.75.57.2]) by
 krone.dialin.utoronto.ca (8.7.5/8.7) with SMTP id VAA00375 for
 <new-httpd@hyperreal.com>; Sun, 5 May 1996 21:31:45 -0400
Date: Sun, 5 May 1996 21:31:45 -0400 (EDT)
Subject: Re: require-client functionality
To: new-httpd@hyperreal.com
In-Reply-To: <199605052008.AA280666880@ooo.lanl.gov>
Message-ID: <ML-2.0.831346305.9124.rasmus@krone.house.mil>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

> depends on you definition of a feature. It'll be compiled in
> (to systems that don't have it) and not used.
> 
> Is that a feature ?   :-)
> 
> It'll make modules for 1.1 easier to write. mod_xinclude.c would
> be a quick plug-in with this for example.

I am not saying it isn't useful.  Currently mod_php links a regexp 
library into the server.  I would much prefer to call a server-based
library since people would then see less of a difference in size of
their PHP-enabled httpd versus their non PHP-enabled version.

However, new features are generally new chunks of code *that can break*
other stuff.  Feature freezes are usually done to stop the introduction
of new code that can cause bugs while concentrating on fixing the existing
code.

-Rasmus