[2652] in Kerberos_V5_Development
Re: Kerberos NT source code
daemon@ATHENA.MIT.EDU (Assar Westerlund)
Fri Oct 24 11:30:26 1997
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Sam Hartman <hartmans@mesas.com>, Ezra Peisach <epeisach@MIT.EDU>,
Ken Hornstein <kenh@cmf.nrl.navy.mil>, krbdev@MIT.EDU
From: Assar Westerlund <assar@sics.se>
Date: 24 Oct 1997 17:30:06 +0200
In-Reply-To: "Theodore Y. Ts'o"'s message of "Fri, 24 Oct 1997 09:49:32 -0400"
"Theodore Y. Ts'o" <tytso@MIT.EDU> writes:
> Well, if so, it'd be nice to get some requirements for application
> developers about exactly how they want to use threads with Kerberos ---
> what parts of the library have to be thread safe against what other
> parts, etc.
Yes. But there seemed to be a few people on krbdev that were
interested in using libkrb5 in multi-threaded applications. Now they
will have to tell us what they want...
> For example, if you're using threads to handle your GUI for a client
> application, there's probably not much we need to do at all. If you're
> using threads for a server application, it would be useful to note how
> people are divvying up the work, and why. (For example, why call
> krb5_rd_req in the listener thread, instead of in the worker thread?
> Are you going to have one thread per connection? Etc.)
I think there's a progressing of different goals here.
1 - simplest case: it should be possible to use different
krb5_context's in different threads without any problem.
2 - consider the cases of 'communicating' *_contexts between different
threads.
/assar
