rfc:ldap_exop

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:ldap_exop [2017/07/04 07:52]
mcmic
rfc:ldap_exop [2017/09/22 13:28] (current)
Line 3: Line 3:
   * Date: 2017-06-26   * Date: 2017-06-26
   * Author: Côme Chilliet, mcmic@php.net   * Author: Côme Chilliet, mcmic@php.net
-  * Status: ​Draft+  * Status: ​Merged
   * First Published at: http://​wiki.php.net/​rfc/​ldap_exop   * First Published at: http://​wiki.php.net/​rfc/​ldap_exop
  
Line 95: Line 95:
  
 ===== Open Issues ===== ===== Open Issues =====
-  - Should the function names contain the word "​exop"​ or is it a technical detail which should be hidden from the developer? 
   - Should we include a constant for LDAP_EXOP_CANCEL,​ for the sake of completeness,​ even if this EXOP won’t be used by PHP code as all PHP LDAP operations are synchrone (in the current code state).   - Should we include a constant for LDAP_EXOP_CANCEL,​ for the sake of completeness,​ even if this EXOP won’t be used by PHP code as all PHP LDAP operations are synchrone (in the current code state).
  
Line 114: Line 113:
  
 ===== Implementation ===== ===== Implementation =====
-After the project is implemented,​ this section should contain ​ +Merged in PHP 7.2 
-  the version(s) it was merged to +https://​github.com/​php/​php-src/​pull/​2608 
-  - a link to the git commit(s)+
   - a link to the PHP manual entry for the feature   - a link to the PHP manual entry for the feature
-  - a link to the language specification section (if any) 
  
 ===== References ===== ===== References =====
rfc/ldap_exop.1499154745.txt.gz · Last modified: 2017/09/22 13:28 (external edit)