Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP-8.4: LDAP changes #4066

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

PHP-8.4: LDAP changes #4066

wants to merge 1 commit into from

Conversation

Girgias
Copy link
Member

@Girgias Girgias commented Nov 14, 2024

I don't understand the ldap_connect() to ldap_connect_wallet() part of UPGRADING, nor do I see how ldap_exop_sync() is seemingly "better" than the current version? The mess of a return type is just duplicated currently....

@Girgias Girgias requested a review from cmb69 November 14, 2024 02:34
@Girgias Girgias added this to the PHP 8.4 milestone Nov 14, 2024
Copy link
Member

@cmb69 cmb69 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand the ldap_connect() to ldap_connect_wallet() part of UPGRADING

See https://wiki.php.net/rfc/deprecate_functions_with_overloaded_signatures#ldap_connect for full details. TL;DR: ldap_connect() should be used when built against OpenLDAP; ldap_connect_wallet() when built against Oracle LDAP (the latter is apparently broken anyway; see https://externals.io/message/125933).

nor do I see how ldap_exop_sync() is seemingly "better" than the current version?

Can't say much about that, except that generally ext/ldap is in thorough need of some TLC.

<listitem>
<para>
The extended operation request data.
May be NULL for some operations like <constant>LDAP_EXOP_WHO_AM_I</constant>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
May be NULL for some operations like <constant>LDAP_EXOP_WHO_AM_I</constant>,
May be &null; for some operations like <constant>LDAP_EXOP_WHO_AM_I</constant>,

<para>
The extended operation request data.
May be NULL for some operations like <constant>LDAP_EXOP_WHO_AM_I</constant>,
may also need to be BER encoded.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe

Suggested change
may also need to be BER encoded.
may also need to be <acronym>BER</acronym> encoded.

(means "Basic Encoding Rules" in this context; however, "Bit Error Rate" seems also pretty common, so there might be an acronym clash)

Copy link
Member Author

@Girgias Girgias Nov 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BER seems to be LDAP specific no? Actually it is a standard known as X.690

Comment on lines +81 to +82
Will be filled with the response OID if provided,
usually equal to the request OID.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe

Suggested change
Will be filled with the response OID if provided,
usually equal to the request OID.
Will be filled with the response <acronym>OID</acronym> if provided,
usually equal to the request <acronym>OID</acronym>.

(means "Object Identifier")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants