rfc:removal_of_dead_sapis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
rfc:removal_of_dead_sapis [2014/01/24 09:02]
ab created
rfc:removal_of_dead_sapis [2017/09/22 13:28] (current)
Line 1: Line 1:
  
 ====== PHP RFC: Removal of dead SAPIs ====== ====== PHP RFC: Removal of dead SAPIs ======
-  * Version: 0.1+  * Version: 0.5
   * Date: 2014-01-24   * Date: 2014-01-24
-  * Author: Anatol Belski, ab@php.net +  * Author: Anatol Belski, <ab@php.net> 
-  * Status: Draft+  * Status: Abandoned is favour of https://wiki.php.net/rfc/removal_of_dead_sapis_and_exts
   * First Published at: http://wiki.php.net/rfc/removal_of_dead_sapis   * First Published at: http://wiki.php.net/rfc/removal_of_dead_sapis
  
 ===== Introduction ===== ===== Introduction =====
 +
 + Currently PHP contains many SAPIs to the servers either completely unavailable or unsupported for a long time. The corresponding list 
  
  Dead SAPIs:  Dead SAPIs:
   * aolserver   * aolserver
   * apache   * apache
-  * apache2filter 
   * apache_hooks   * apache_hooks
   * caudium   * caudium
   * continuity   * continuity
   * isapi   * isapi
-  * litespeed +  * milter  
-  * milter +
-  * nsapi+
   * phttpd   * phttpd
   * pi3web   * pi3web
Line 26: Line 25:
   * tux   * tux
   * webjames   * webjames
 +  * apache2filter - not really dead, but currently broken
  
  Maintained SAPIs:  Maintained SAPIs:
Line 33: Line 33:
   * embed   * embed
   * fpm   * fpm
 +  * litespeed
 +  * nsapi
   * phpdbg   * phpdbg
  
-===== Proposal =====+\\ 
 +Things required to be done for the final decisions: 
 +  * research the author names 
 +  * articulate the exact state of each dead SAPI 
 +  * articulate the exact state and availability of the corresponding server 
 +  * if possible and makes sense, check if the SAPIs compiles, even with very ancient but latest release of the server 
 +  * check if there are packages supported by distros 
 +  * notify the authors about a possible removal of the corresponding SAPI, wait for their response and include it for the final decision
  
-All the features and examples of the proposal.+This RFC crosses with https://wiki.php.net/rfc/size_t_and_int64 as removal of the dead SAPIs will exlude the need of their porting. 
 + 
 +===== Proposal =====
  
-To [[http://news.php.net/php.internals/66051|paraphrase Zeev Suraski]], explain hows the proposal brings substantial value to be considered +Dead SAPIs should be removed.
-for inclusion in one of the world's most popular programming languages.+
  
-Remember that the RFC contents should be easily reusable in the PHP Documentation. 
 ===== Backward Incompatible Changes ===== ===== Backward Incompatible Changes =====
  
-What breaksand what is the justification for it?+As the dead SAPIs are already deadno BC breach is expected.
  
 ===== Proposed PHP Version(s) ===== ===== Proposed PHP Version(s) =====
  
-List the proposed PHP versions that the feature will be included in.  Use relative versions such as "next PHP 5.x" or "next PHP 5.x.y".+7
  
 ===== SAPIs Impacted ===== ===== SAPIs Impacted =====
  
-Describe the impact to CLI, Development web server, embedded PHP etc.+Dead SAPI list in the description.
  
 ===== Impact to Existing Extensions ===== ===== Impact to Existing Extensions =====
  
-Will existing extensions be affected? +None.
- +
-===== New Constants ===== +
- +
-Describe any new constants so they can be accurately and comprehensively explained in the PHP documentation.+
  
 ===== php.ini Defaults ===== ===== php.ini Defaults =====
  
-If there are any php.ini settings then list: +php.ini will have to be checked to remove the unavailable config options, if any.
-  * hardcoded default values +
-  * php.ini-development values +
-  * php.ini-production values+
  
 ===== Open Issues ===== ===== Open Issues =====
  
-Make sure there are no open issues when the vote starts!+None.
  
 ===== Unaffected PHP Functionality ===== ===== Unaffected PHP Functionality =====
  
-List existing areas/features of PHP that will not be changed by the RFC. +None.
- +
-This helps avoid any ambiguity, shows that you have thought deeply about the RFC's impact, and helps reduces mail list noise.+
  
 ===== Future Scope ===== ===== Future Scope =====
  
-This sections details areas where the feature might be improved in future, but that are not currently proposed in this RFC.+Should an SAPI come back, the corresponding code is available in the git history.
  
 ===== Proposed Voting Choices ===== ===== Proposed Voting Choices =====
  
-Include these so readers know where you are heading and can discuss the proposed voting options.+Remove dead SAPIs: yes/no
  
 ===== Patches and Tests ===== ===== Patches and Tests =====
rfc/removal_of_dead_sapis.1390554127.txt.gz · Last modified: 2017/09/22 13:28 (external edit)