rfc:ldap_exop

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
rfc:ldap_exop [2017/06/29 14:33] mcmicrfc:ldap_exop [2017/09/22 13:28] (current) – external edit 127.0.0.1
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 31: Line 31:
 This RFC also wish to introduce helper functions for common EXOP usage: This RFC also wish to introduce helper functions for common EXOP usage:
 <code php> <code php>
-bool ldap_exop_whoami(resource $link, string &$result+bool|string ldap_exop_whoami(resource $link) 
-bool ldap_exop_passwd(resource $link, string $user, string $oldpw, string $newpw [, string &$genpw])+bool|string ldap_exop_passwd(resource $link, [string $user, [string $oldpw, [string $newpw]]])
 </code> </code>
-The first one would call whoami EXOP and fill $result with the result. Return TRUE or FALSE upon failure. +The first one would call whoami EXOP and returns the result. Returns FALSE upon failure. 
-The second one would call passwd EXOP and return TRUE or FALSE upon failure. If $newpw is empty, $genpw will be filled with the generated password for the user. If $user is empty, it affects the bound user.+The second one would call passwd EXOP and return TRUE or FALSE upon failure. If $newpw is empty, returns the generated password for the user. If $user is empty, it affects the bound user.
  
 The author of the original patch stated that technically ldap_start_tls is an exop helper and therefore could be renamed ldap_exop_start_tls. We feel this would be a useless BC. The author of the original patch stated that technically ldap_start_tls is an exop helper and therefore could be renamed ldap_exop_start_tls. We feel this would be a useless BC.
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.1498746817.txt.gz · Last modified: 2017/09/22 13:28 (external edit)