James Carlson wrote: > > > The native Solaris LDAP and OpenLDAP SDKs implement some of the > > same symbols. Any libraries loaded into the same process as > > APR-Util and Apache must use the same LDAP SDK, or the behavior > > is undefined. > > > > Other users of the OpenSolaris-delivered OpenLDAP client library > > should understand that the interfaces are Volatile and hence may > > change in an incompatible manner in the future. > > I don't think switching from the native Solaris LDAP to the OpenLDAP > library is either obvious or non-controversial. My read of 2008/507 > suggests that OpenLDAP was intended to allow others to use the library > if wanted (and despite the compatibility risks it poses), and not as a > way for us to deliver software. > > Are you sure this is indeed a fast-track?
It's obvious and non-controversial to me. Opinions may differ. It is also sub-optimal, but that's not a criteria. In an alternate universe where Solaris LDAP team is resourced, it'd be good if they fix the OpenLDAP compatibility either by switching to OpenLDAP or making Sun's LDAP fully compatible. Three years later we're still waiting for the Solaris LDAP team (if such a team exists anymore) to get resourced to do something as simple as updating the version of the library (called out in WSARC/2006/582) so the chances of getting to more involved work are nil. The Apache/APR project team has done a good job investigating and documenting in detail all the issues. Jeff has an AI to follow up on Danek's earlier suggestion, beyond that there's not much more left to say. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
