transitioning release management

[Derrell Lipman]

On Wed, Feb 27, 2008 at 2:15 PM, Volker Lendecke
<Volker.Lendecke at sernet.de> wrote:
>  What would your extensible API look like?

The big change is that instead of the user manipulating structure
members in the context structure, the context structure will become
entirely opaque, and setter and getter functions will be used for
changing it.  This allows me to make changes to the internal context
structure, typically for adding new functionality, without affecting
the ABI.  While I'm at it, I'll clean up the use of the different
types of option settings (there are currently three different
mechanisms in use!) and the authentication callback function.

>  Assuming that my proposal for the async client libs is
>  something that we want (I definitely want this), is there a
>  sane way we can expose this async functionality to the user?
>  And, is there a sane way to plug into different event loops?

The event loop stuff all happens "under the hood" right now.  The user
has no control over it.  (All functions are synchronous.)  It will be
possible to make changes for async usage later, keeping the existing
functions as wrappers which call the send and receive functions like
the wrappers in Samba4 do.

>  While there, what are the important event architectures out
>  there that we need to support? glib? Do they have one? KDE?
>  libevent? What else is out there?

dbus is what's used by KDE and seems to be quite popular.  I haven't
yet had an opportunity to look into it in depth, but it's on my list
of things to do "one of these days".

Derrell