Message-ID: <37D58FB4.D2940F1E@algroup.co.uk>
Date: Tue, 07 Sep 1999 23:20:36 +0100
From: Ben Laurie <ben@algroup.co.uk>
Organization: A.L. Group plc
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: STANDARD20_MODULE_STUFF
References: <199908271823.aa28908@gremlin-relay.ics.uci.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

"Roy T. Fielding" wrote:
> 
> >> Hmmm, a more general solution would be to add a
> >>
> >>   #define APACHE_GENERATION 2
> >>
> >> at the top of each updated module, and then check for it in one of the
> >> required module includes.  That way we could print out a nice error
> >> message that says the source is incompatible and where to find
> >> information on updates.
> >
> >look in http_config.h:
> >
> >#define STANDARD_MODULE_STUFF   this_module_needs_to_be_ported_to_apache_2_0
> 
> By more general solution, I meant something that wasn't tied to a specific
> version of the server. I'd hate to have to explain that change within
> a book on module programming.  We should implement something that can
> anticipate the next time we need to force a compile error.

I'm with Dean on this one: anticipating all the compile errors you may
want to force is a) hopeless, and b) a waste of time. But then, I'm an
ignorant slut. What do I know?

Cheers,

Ben.

--
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