httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carla Schroder <>
Subject response to comments re: API changing
Date Fri, 25 Oct 2002 19:15:11 GMT
Hello excellent Apache developers,

I am writing a feature on Apache 2 for It will cover new 
features, and quotes from users on why they are, or are not, upgrading from 
1.3. (Besides 'if it ain't broke don't fix it') 

Would any of you care to address the following comment? This is from the IT 
director at a local ISP. Is this really an issue?

"We are already using it for several sites.....the biggest problem that we 
(and many others) have with deploying it everywhere is that the API hasn't 
yet stabilized, so
modules, such as PHP, have to be recompiled and often slightly modified to
get them to work every time Apache issues a new release. This is a pain as
we often have to wait for days or weeks before all of modules that we may
want to use have instructions on what to modify.

"We are apprehensive about using it in shared hosting because we don't
consider it release-quality software.  We and many others (including the PHP
development team) feel the Apache Software Foundation released it
prematurely.  Most notably, they continue to change core APIs on point
releases, an established no-no in the open source development paradigm for
supposed stable, released software."

I'd like to hear from the actual developers on this! I read back several 
months in the list archives, to get some background.

Thanks much,
Carla Schroder
Bratgrrl Computing
This message brought to you by
Red Hat 8 and Kmail

View raw message