[2651] in Kerberos_V5_Development
Re: Kerberos NT source code
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Fri Oct 24 09:49:51 1997
Date: Fri, 24 Oct 1997 09:49:32 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Assar Westerlund <assar@sics.se>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, Sam Hartman
<hartmans@mesas.com>,
Ezra Peisach <epeisach@MIT.EDU>,
Ken
Hornstein <kenh@cmf.nrl.navy.mil>, krbdev@MIT.EDU
In-Reply-To: Assar Westerlund's message of 24 Oct 1997 11:49:09 +0200,
<5lyb3j32zu.fsf@assaris.sics.se>
From: Assar Westerlund <assar@sics.se>
Date: 24 Oct 1997 11:49:09 +0200
Religion apart (:-), there seems to be a demand for using threads with
libkrb5 so I think we should decide and specify a supported way of
doing that and implement it.
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.
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.)
- Ted
