Previous experience has shown it can take nearly a year after a release before a large proportion of sites upgrade. This situation causes a dilema for programmers working on Apache. Some minor feature additions have been added to Apache 1.3 but there are a number of larger patches that have not yet been accepted. It is not currently known if any of these will be included in a future release of 1.3, or if they will have to wait until 2.0. EAPI EAPI is one solution for modules that need to take more control of Apache than the current Apache API allows.
Many modules can make use of such a mechanism.
With so many sites already patching in EAPI to their 1.3 servers it would be sensible to include EAPI in a future 1.3 release, but this would make it incompatible with Apache 2.0 which already contains a different hook mechanism. These patches are optimised for the SGI Irix platform where they gave up to a ten-fold increase in speed. It has been decided that these patches will not be included in Apache 1.3 but they may be included in Apache 2.0. Users of Apache 1.3 who are interested in trying out the improvements can download the patches direct from SGI . Apache Week is a sponsor of ApacheCon 2000 and will keep you updated on conference news between now and March.