[79] in pc-kerberos
Naming conventions of DLLs?
daemon@ATHENA.MIT.EDU (Paul B. Hill )
Fri Apr 28 12:11:42 1995
To: pc-kerberos@MIT.EDU
Cc: dosdev@MIT.EDU, tytso@MIT.EDU, jmr@fusion.com, keithv@fusion.com,
eichin@cygnus.com
Date: Fri, 28 Apr 95 11:59:56
From: pbh@MIT.EDU (Paul B. Hill )
Reply-To: pc-kerberos@MIT.EDU
Hi,
As most of you know we changed the name of our Kerberos DLL last summer. It
went from krbdll.dll to krbv4win.dll and we created a new DLL called
krbv4os2.dll.
As we're working on a some new DLLs I'd like to propose some more naming
conventions. By adhering to these conventions win16 applications should
continue to function correctly on OS/2, NT, and Win'9?.
krbv4win.dll -- win16 Kerberos version 4 (released) (new release this summer)
krbv4os2.dll -- native OS/2 Kerberos version 4 (released) (ditto)
krbv432.dll -- win32 Kerberos version 4 (in development)
I think we should follow the same naming convention for Kerberos version 5.
krbv5win.dll -- win16 Kerberos version 5 (in beta as krbv5.dll)
krbv5os2.dll -- OS/2 Kerberos version 5 (no active development at this time)
krbv532.dll -- win32 Kerberos version 5 (in development)
Now the GSS-API naming convention becomes trickier. The IETF draft for the
GSS-API V1 MS Windows Dynamic Link Library Interface specifies the
bindings in the win16 environment. The draft also specifies the name of the
DLL as GSSAPI.DLL.
gssapi.dll -- win16 GSS API (in beta)
gssapio2.dll -- OS/2 GSS API (no work at this time)
gssapi32.dll -- win32 GSS API (in development)
Although our wshelper.dll is not related to Kerberos I'd like to propose our
future naming conventions for it at this time.
wshelper.dll -- win16 version (for historical reasons) (released)
wshelpo2.dll -- OS/2 version (no work at this time)
wshelp32.dll -- win32 version (no work at this time)
The reason that I have kept all names to the 8.3 naming convention is that
we cannot safely assume that the win32 or OS/2 DLLs will be stored on HPFS
or NTFS drive partions.
Our Kerberos version 4 DLLs do not have the same name(s) as the Cygnus
version 4 DLLs. At this time the C bindings are different and there are some
different features. We hope to co-operate with Cygnus over the next year to
converge the two releases.
Cygnus is doing the work on the win16 version 5 and GSS API DLLs. MIT is
providing the funding and will do the work on the NT and possibly OS/2
versions. There should be NO divergence because of this close working
relationship.
Please let me know if you have any objections to these naming conventions as
soon as possible. Replies should go the pc-kerberos@mit.edu list.
Paul
