Asynchronous operation and krb5 dependencies

Nico Williams nico at cryptonector.com
Wed Jun 8 15:25:55 EDT 2011


On Mon, Jun 6, 2011 at 9:48 AM, Simo Sorce <simo at redhat.com> wrote:
> I would strongly advice for passing a context, you can pass it down
> easily, and should you decide to not use it later, you can simply set it
> to NULL, or ignore the argument. But adding a new interface w/o a
> context is calling for trouble later IMHO.

+1.  We've made this mistake of not having a caller context in too
many APIs.  Let us stop making this mistake now.

Nico
--



More information about the krbdev mailing list