[2623] in Kerberos_V5_Development
Re: Kerberos NT source code
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Oct 22 12:00:48 1997
To: Assar Westerlund <assar@sics.se>
Cc: Ezra Peisach <epeisach@MIT.EDU>, Ken Hornstein <kenh@cmf.nrl.navy.mil>,
krbdev@MIT.EDU
From: Sam Hartman <hartmans@mesas.com>
Date: 22 Oct 1997 10:59:40 -0500
In-Reply-To: Assar Westerlund's message of 22 Oct 1997 17:42:31 +0200
>>>>> "Assar" == Assar Westerlund <assar@sics.se> writes:
Assar> Ezra Peisach <epeisach@MIT.EDU> writes:
>> The question is whether the krb5_context is a per process or a
>> per thread context.... If it is per thread - i.e. a new one for
>> each thread, I suspect that many of the problems could be
>> trivially solved.
Assar> So, do we have anyone who is trying or contemplating
Assar> writing multi-threaded kerberised code that can tell us how
Assar> they would want it to be?
Having a per-thread context would be much more reasonable if
you could move auth contexts from one context to another. You want to
be able to listen, do a krb_rd_req, queue the request to be handled by
a worker thread, and have the listener continue its work.
Assar> /assar
