Exactly -
It would be one thing if each library had a lot of non-standard calls
(i.e. different functions) that performed generally the same tasks - but
that is not what is happening here.
sterling
On Tue, 21 Aug 2001, Ryan Bloom wrote:
>
> Woah. Those are build differences, not C-code differences. Those can
> all be handled with some simple m4 configure scripts. Why are we wrapping
> C-code? What differences are we abstracting with the C code?
>
> Ryan
>
> On Tuesday 21 August 2001 11:54, Graham Leggett wrote:
> > sterling wrote:
> > > > Well, it did have a portability function in that it smoothed out
> > > > differences between various LDAP libraries (openldap/netscape/iplanet)
> > > > rather than various platforms (unix/nt/etc).
> > >
> > > what differences are smoothed out? maybe i'm looking in the wrong place,
> > > but i don't see any of this functionality.
> >
> > Openldap:
> >
> > - uses ldap.h, lber.h
> > - links to libldap and liblber
> > - supports STARTTLS
> >
> > Netscape
> >
> > - uses ldap.h, lber.h, ldap_ssl.h
> > - links to libldapssl(20|30|40|41)
> > - supports SSL, but not TLS
> >
> > iPlanet
> >
> > - header files???
> > - links to libldap50 and these: "-lnspr4 -lplc4 -lplds4 -liutil50
> > -llber50 -lldif50 -lnss3 -lprldap50 -lssl3 -lssldap50"
> > - SSL support, TLS support unknown
> >
> > Active Directory
> >
> > - ???
> >
> > In addition there are a whole bunch of differences depending on whether
> > you're using LDAP v2.0 or v3.0 - see apr_ldap_compat.c.
> >
> > Regards,
> > Graham
>
> ----------------------------------------
> Content-Type: application/x-pkcs7-signature; charset="us-ascii"; name="smime.p7s"
> Content-Transfer-Encoding: base64
> Content-Description: S/MIME Cryptographic Signature
> ----------------------------------------
>
>
