Re: Future of ldapmodule

[<fo...@mi...>]

Scavenging the mail folder uncovered Michael Ströder's letter:
> I would suggest that ldapmodule stays as close to the C API as
> possible with having exception for error handling just as it is
> right now. Higher level abstractions (all kind of schema handling)
> can be build into a separate Python class library (e.g. fog's
> modules).

i agree. michael, last time you were suggesting various changes to
my implementation, mainly to deal with schema. can you elaborate a
little bit more? i think you had better ideas then me on the argument
and i don't want to start piling up code without your 

some general questions:

has somebody tried my wrapper module or the lappo client? i didn't
received any comments on both.

any release of python-ldap at the horizon? i like much better to release
and get feedback than try do do all right from the start :)

ciao,
federico

> For me as a LDAP client programmer there are two main issues which
> can only be solved within the C module:
> 
> - LDAPv3
>   (I have to at least be able to tell the server that my program
>   is a LDAPv3 client.)
> - SSL
> 
> Both features can be achieved by sitting on top of the Netscape
> library found on http://www.mozilla.org/. I think we should reach
> the same level like PerlLDAP (also found on Mozilla).

yes, but i think the best thing is to not force a particular library
upon the user but let him choose... (autoconf/automake?)

-- 
Federico Di Gregorio
MIXAD LIVE System Programmer                           fo...@mi...
Debian GNU/Linux Developer & Italian Press Contact        fo...@de...
              All programmers are optimists. -- Frederick P. Brooks, Jr.