rfc:apxs-loadmodule
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:apxs-loadmodule [2012/02/27 01:22] – See changelog; 1.20. kriscraig | rfc:apxs-loadmodule [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Request for Comments: APXS LoadModule Option in configure ====== | ====== Request for Comments: APXS LoadModule Option in configure ====== | ||
- | * RFC Version: 1.20 | + | * RFC Version: 1.40 |
* Target PHP Version: 5.4.1 | * Target PHP Version: 5.4.1 | ||
* Date: 2012-02-20 | * Date: 2012-02-20 | ||
* Author: Kris Craig < | * Author: Kris Craig < | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 61: | Line 61: | ||
* Apache 1.3.x was officially " | * Apache 1.3.x was officially " | ||
- | * According to an informal poll conducted by cPanel about a year ago, 91% of their uses report that they use Apache 2.x instead of 1.3.x in all circumstances. | + | * According to an informal poll conducted by cPanel about a year ago, 91% of their users report that they use Apache 2.x instead of 1.3.x in all circumstances. |
* Of all the requests for this feature I have seen that were posted in recent years, I have not been able to find a single one who was using Apache 1.3.x instead of 2.x. | * Of all the requests for this feature I have seen that were posted in recent years, I have not been able to find a single one who was using Apache 1.3.x instead of 2.x. | ||
* Keeping 1.3.x support for legacy compatibility does not necessitate continuing to apply new features to it. On the contrary, continuing to expend resources (even a small amount as would be the case this time) supporting something that its makers already EOL'd a long time ago would set a bad precedent. | * Keeping 1.3.x support for legacy compatibility does not necessitate continuing to apply new features to it. On the contrary, continuing to expend resources (even a small amount as would be the case this time) supporting something that its makers already EOL'd a long time ago would set a bad precedent. | ||
Line 74: | Line 74: | ||
It occurred to me that the next logical step would be to expand this so that the user could opt to create a separate configuration file (i.e. php.conf) and have an include directive added to httpd.conf if it's not already there. | It occurred to me that the next logical step would be to expand this so that the user could opt to create a separate configuration file (i.e. php.conf) and have an include directive added to httpd.conf if it's not already there. | ||
+ | |||
+ | ===== Vote ===== | ||
+ | |||
+ | [[rfc/ | ||
===== Changelog ===== | ===== Changelog ===== | ||
+ | |||
+ | Version 1.40 : Status => [[rfc/ | ||
+ | |||
+ | Version 1.30 : Voting. | ||
+ | |||
+ | Version 1.21 : Typo correction. | ||
Version 1.20 : Content revisions based on PHP Internals discussions. | Version 1.20 : Content revisions based on PHP Internals discussions. |
rfc/apxs-loadmodule.1330305748.txt.gz · Last modified: 2017/09/22 13:28 (external edit)