home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.kerberos
- Path: sparky!uunet!news.centerline.com!noc.near.net!vaxeline.ftp.com!minimillian.ftp.com!backman
- From: backman@vaxeline.ftp.com (Larry Backman)
- Subject: Re: Kerberos for DOS and OS/2
- Message-ID: <920911110733@minimillian.ftp.com>
- Nntp-Software: PC/TCP NNTP
- Lines: 24
- Sender: root@vaxeline.ftp.com (vaxeline.ftp.com root account)
- Nntp-Posting-Host: minimillian.ftp.com
- Organization: FTP Software, Inc., Wakefield, MA
- References: <9209012341.AA22373@endor.harvard.edu>
- Date: Fri, 11 Sep 1992 11:07:33
-
- In article <9209012341.AA22373@endor.harvard.edu> ddl@DAS.HARVARD.EDU (Dan Lanciani) writes:
-
- >> |Is your krb for OS/2 process or thread reentrant?
- >>
- >> It is, by definition, process-reentrant. I have no idea how
- >> it would react to multi-threading as there many potential critical
- >> sections. Tracking them down will have to wait until I have an
- >> application that can make real use of multi-threading (beyond being able
- >> to call itself a multi-threaded application in PR releases :).
- >>
- >> |i.e., is it in a
- >> |DLL that can be shared by processes and threads?
- >>
- >> I never bothered building a DLL; however, FTP Software packages
- >> the code as a DLL so it can certainly be done.
- >>
- As Dan says we ship the kerberos code as a Kerberos DLL. It most certainly
- is multi-process reentrant and most probably would break if you wrote a
- mutl-threaded app that used kerberos services concurrently.
-
- Our experience so far over the 1.5 years we have been shipping the DLL
- is limited; there are few users of OS/2 and fewer even of OS/2 & Kerberos.
-
- L.
-
-