[proof of concept] libwbclient.so

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Volker,

> One main question for me is: How much of the winbind pipe do
> we want to expose via an API that we stick to in the future?
> For example, what about the DC lookup routines that gd has
> added recently for his krb5 locator plugin? How do we handle
> changes here? 

My goal is that this library should be the only way
that smbd communicates with winbindd.  So therefore if a
fucntion is necessary added smbd, it must be added to the
library.  I want to remove all compile time static links
between smbd and winbindd.

> Is that library similar to the Linux kernel syscall API
> (never remove anything)?

Good question.  We can make incompatible changes in
major library version increments.  But I think that we
have to postpone this discussion until we have something
real to talk about.

Bottom line is that I believe we should be willing to commit
to an API that other people can trust and use and that this API
should mirror the winbindd pipe protocol commands.




cheers, jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG1raVIR7qMdg1EfYRAvrcAKCpqEg4aJ1DxvXeLvGAj4WW5Tvu5wCgtqTG
V7w5pvAACAu6Z8ABe61p0KQ=
=cLHX
-----END PGP SIGNATURE-----