Avoiding further (LDAP) stack proliferation in Samba

[Karolin Seeger]

Hi,

Am 09.06.20 um 01:17 schrieb Christof Schmitt via samba-technical:
> Hi Andrew,
> 
> as Metze wrote, there is still work to be done across tldap and ldb, and
> probably more questions will come up, which libraries to re-use, how to
> handle dependencies to those, etc.
> 
> For winbindd, the long-tem goal is to improve failover to different
> domain controllers, in case of network problems or DC outages. The
> current problem today is that winbindd uses libads, which encapsulates
> DC selection, LDAP queries and retries in a way that is completely
> outside of the control of winbindd. So the idea is to move winbindd to
> tldap first, and then later on move winbindd to be fully async, avoid
> the child processes and keep the connection state in one place.
> 
> The goals to unify the LDAP stacks are worthwhile, but i do not see
> those as necessary for the winbindd changes. I suspect that would also
> trigger a wider discussion, e.g. which ASN.1 library to use, how to
> reprent common data structures, where to put these to handle
> dependencies.

I do fully agree on this! Why can't we go ahead with tldap now (which is
used in other places also) to fix the bug and do the re-design later?

Cheers,
Karolin

-- 
Karolin Seeger			https://samba.org/~kseeger/
Release Manager Samba Team	https://samba.org
Team Lead Samba SerNet		https://sernet.de