updated TODO

doc/TODO

@@ -2,46 +2,62 @@
 
 * Missing functionality
  
-** Server/Client-controls
+** server/client-controls and/or _ext() functions
-   plus all _ext_s() functions:
-     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()
 
-* Fixing needed
+   The functions make use of server/client-controls and/or are
+   _ext()-functions and are currently not supported:
 
-* Need ber-stuff first
+   ldap_unbind_ext()
-  ldap_sasl_bind_s()
+   ldap_search_ext_s()
-  ldap_first_attribute()
+   ldap_compare_ext_s()
-  ldap_next_attribute()
+   ldap_modify_ext_s()
-  ldap_get_value_len()
+   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()
 
-* Not implemented
+** BER-stuff
-  
-** Check for errors in ldap_{first, next}_{entries, references, messages}
 
-   These functions may return S48_FALSE if the corresponding C
+   The functions are missing because there is only very basic support
-   function returns NULL.  This is ambigious: a) end of list b) error
+   for the BER-stuff:
-   solution: check for error in Scheme
 
-  ldap_explode_dn()
+   ldap_sasl_bind_s()
-  ldap_explode_rdn()
+   ldap_first_attribute()
-  ldap_dn2ufn()
+   ldap_next_attribute()
+   ldap_get_value_len()
 
-  ldap_get_entry_controls()
+** structures and accessors
-  
-  ldap_parse_reference()
-  
-* 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?