Re: KITTEN: IETF 75 - 76

[Michael B Allen <miallen at ioplex.com>]

On Thu, 03 Sep 2009 10:38:49 -0400
Jeffrey Hutzelman <jhutz at cmu.edu> wrote:
> > There is another model:
> >
> >> > while (1) {
> >         gss_process_events(&minor, ...);
> >> >
> >> > 	ret = gss_call(&minor, GSS_C_NOWAIT, ...);
> >> > 	if (ret != 0 && minor == EAGAIN) {
> >> > 		continue;
> >> > 	}
> >> > 	...
> >> > 	break;
> >> > }
> 
> That's not another model.  That's equivalent to using the synchronous form 
> of the call, if gss_process_events() blocks until the mech is ready to be 
> called, or to polling, if it eventually times out.

But there only needs to be one caller of gss_process_events for any number of NOWAIT calls. So you can build event loops with it. I'm not sure I understand the callback model being discussed but it seems to be an event loop powered by a separate thread firing callbacks in response to changes in status of calls. If that is in fact the case, you could build the callback model you're talking about using only the NOWAIT flag model I'm talking about.

Mike

-- 
Michael B Allen
Java Active Directory Integration
http://www.ioplex.com/