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

preparation for the next release #18

Merged
merged 11 commits into from Mar 29, 2013
Merged

preparation for the next release #18

merged 11 commits into from Mar 29, 2013

Conversation

marschap
Copy link
Contributor

No description provided.

Thanks to Carsten Dumke <Carsten.Dumke@gmx.net> for reporting it.
Although not required by the RFC, Base64-encode those values that end in
spaces when writing LDIFs.
This makes it easier for the user to visually detect those values and
increases compatibility with other implementations (e.g. OpenLDAP's
ldapsearch).
LDIF change records may contain 'control:' stanzas.
Instead of chocking on them when reading, decode them properly.

In this commit, the controls read are not returned to the caller,
they are only parsed in Net::LDAP::LDIF internally and ignored.
This is done in order to leave the API unchanged.
When operating on the standard IO handles, treat mode 'a'/'>>' (append)
the same way as mode 'w'/'>' (write) instead of 'r'/'<' (read).

Allow using the "translated" mode codes too: '<', '>', and '>>'.

Use 3-parameter open when possible.

Rearrange the code slightly to make it more readable.
marschap added a commit that referenced this pull request Mar 29, 2013
preparation for the next release
@marschap marschap merged commit c85d864 into perl-ldap:next Mar 29, 2013
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.

None yet

1 participant