[2650] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Kerberos NT source code

daemon@ATHENA.MIT.EDU (Assar Westerlund)
Fri Oct 24 05:48:43 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 11:49:09 +0200
In-Reply-To: "Theodore Y. Ts'o"'s message of "Thu, 23 Oct 1997 14:21:21 -0400"

"Theodore Y. Ts'o" <tytso@MIT.EDU> writes:
> I was concerned about future implementations where you might play
> tricking games with allocation and deallocation routines which might be
> more restrictive than malloc.  We have that to some extent in Windows
> DLL's --- it's not necessarily safe to have a calling application call
> free() on something allocated by a DLL, because (a) they may be using a
> different libc, with a different malloc, and (b) because they be
> allocating out of completely different memory pools.  

Ok, I can see that I can be a problem in the future.

> I still think there are many problems for which it is technically
> possible to use threads, but it's not always clear that threads are the
> best way to solve that problem.

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.

/assar

home help back first fref pref prev next nref lref last post