IMHO: Winbind in Samba4 (Was: winbind in samba4?)

[Richard Sharpe]

On Sat, 8 Jan 2005, Stefan (metze) Metzmacher wrote:

> I think winbind is very important for samba4 because it will be act as proxy for
> rpc communication with trusted domains dc's
>
> and for a member server/workstation the primary domain is also just a simple trusted domain
>
>
> | I think the most urgent things are:
> | -Samba4 LDAP Server
> | -DRSUAPI replication
> | -LDB rewriting (with the new talloc code)
> | -Heimdal integration (read-write ldb backend, more PAC testing)

I can imagine a winbindd in samba4 that has a single work queue, where
objects are placed on the work queue. These objects are things like
requests, connections, timer events etc. Since Samba4's underlying model
makes RPC and SMB requests and responses separable things, once an SMB or
RPC request for a winbindd request has been sent, that winbindd request
object could go back on the bottom of the queue and be handled again when
the response comes back in.

Of course that means state machines for each winbindd request. A careful
design might also require multiple queues as access to netlogon pipes etc
will need to be serialized, but so be it.

WRT co-routines. We use continuations at work, which are a little like
co-routines. That way madness lies!

Regards
-----
Richard Sharpe, rsharpe[at]richardsharpe.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com