63 lines
1.4 KiB
Plaintext
63 lines
1.4 KiB
Plaintext
-*- outline -*-
|
|
|
|
* Missing functionality
|
|
|
|
** server/client-controls and/or _ext() functions
|
|
|
|
The functions make use of server/client-controls and/or are
|
|
_ext()-functions and are currently not supported:
|
|
|
|
ldap_unbind_ext()
|
|
ldap_search_ext_s()
|
|
ldap_compare_ext_s()
|
|
ldap_modify_ext_s()
|
|
ldap_rename_s()
|
|
ldap_add_ext_s()
|
|
ldap_delete_ext_s()
|
|
ldap_extended_operation_s()
|
|
ldap_abandon_ext()
|
|
ldap_parse_result()
|
|
ldap_parse_sasl_bind_result()
|
|
ldap_parse_extended_result()
|
|
ldap_get_entry_controls()
|
|
ldap_parse_reference()
|
|
|
|
** BER-stuff
|
|
|
|
The functions are missing because there is only very basic support
|
|
for the BER-stuff:
|
|
|
|
ldap_sasl_bind_s()
|
|
ldap_first_attribute()
|
|
ldap_next_attribute()
|
|
ldap_get_value_len()
|
|
|
|
** structures and accessors
|
|
|
|
struct berval
|
|
struct ldapmod
|
|
|
|
* Testing needed
|
|
|
|
Except for the function to basic searching you should consider all
|
|
functions as untested. ;-)
|
|
|
|
* Known bugs
|
|
|
|
** GC bug
|
|
There is a serious bug while freeing LDAP-structures. Sometimes
|
|
free is called several times for the same object --- may lead to
|
|
crashes. My plan: seek & destroy
|
|
|
|
** Pointers from message back to session
|
|
Is this a good idea or is it the source of all evil?
|
|
|
|
* Design
|
|
|
|
Almost all LDAP-calls need the session-handle. Make it a
|
|
fluid. There really should be a CURRENT-LDAP-SESSION,
|
|
WITH-CURRENT-LDAP-SESSION etc.
|
|
|
|
* Documentation
|
|
|
|
What documentation? |