[2185] in Kerberos_V5_Development
Re: Comments on Krb5-nt-alpha1 - DLL / Application Problems
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Sun Jan 26 20:20:00 1997
To: deengert@anl.gov
Cc: krbdev@MIT.EDU
From: Ken Raeburn <raeburn@cygnus.com>
Date: 26 Jan 1997 20:19:28 -0500
In-Reply-To: "Douglas E. Engert"'s message of Sat, 25 Jan 1997 14:08:08 -0600
"Douglas E. Engert" <deengert@anl.gov> writes:
> As an enhancement for future applications, I would like to suggest the
> these macros be converteted to routines which are then exported. This
> then means that none of the crypto routines needs to be exported, which
> will help with future releases as new routines are added, they will
> become accessable to older applications as well.
I'd suggest that nearly all the function-style macros should have real
function equivalents anyways.
If they're available as functions, we don't need the macros. We might
want them as optional optimizations, maybe. But I think having a
simple and reasonable interface is more important than boosting the
performance slightly by making interfaces more complicated.
If we don't provide the macros, maybe we don't need to provide the
data structures' internals.
If we don't provide the data structure internals, the API becomes
smaller. And it's easier to change the implementation without
affecting exported interfaces.
> This two can be solved by having a routine in the DLL to free
> memory obtained by the DLL.
I think this is a good idea too, and not just for NT.
Ken
