[16867] in Kerberos_V5_Development
Re: Asynchronous operation and krb5 dependencies
daemon@ATHENA.MIT.EDU (Nico Williams)
Wed Jun 8 15:26:01 2011
MIME-Version: 1.0
In-Reply-To: <1307371697.2613.155.camel@willson.li.ssimo.org>
Date: Wed, 8 Jun 2011 14:25:55 -0500
Message-ID: <BANLkTi=wagRxr8G_HFdGXJJT1AZzXCGDPA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Simo Sorce <simo@redhat.com>
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Mon, Jun 6, 2011 at 9:48 AM, Simo Sorce <simo@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
--
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
