Re: KITTEN: IETF 75 - 76

[Nicolas Williams <Nicolas.Williams at sun.com>]

On Tue, Sep 01, 2009 at 03:39:33PM -0700, Love Hörnquist Åstrand wrote:
> 1 sep 2009 kl. 15:20 skrev Nicolas Williams:
> >I agree.  Callbacks are easy.  My construction (for ISC) is simpler:
> >no need for all the ISC output args in the callback.
> 
> So what is input token for the second call ? Can input token be freed  
> between first and second call ?

It should be the same as in the previous call.  But that can be relaxed
-- we could say that the mech must keep an internal copy if it will
continue needing it after the first call.

> Why do I have to pass all those argument that might (or might not) do  
> something.

If it's hard to track them you can always place them in the callback
function's argument -- a void * that would be a pointer to a struct with
all the context that the callback needs, including those GISC args if
you're not storing them elsewhere.