home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!slc6!trier
- From: trier@slc6.ins.cwru.edu (Stephen C. Trier)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: Winsock available?
- Date: 18 Dec 1992 19:05:42 GMT
- Organization: Case Western Reserve University, Cleveland OH (USA)
- Lines: 25
- Message-ID: <1gt7e6INNhj0@usenet.INS.CWRU.Edu>
- References: <1992Dec16.064550.16314@microsoft.com> <BzGuFA.4FG@cedb.dpcsys.org>
- NNTP-Posting-Host: slc6.ins.cwru.edu
-
- In article <BzGuFA.4FG@cedb.dpcsys.org> dan@cedb.dpcsys.org (Dan Busarow) writes:
- >Are there any plans to develop a 'winsock' API library which could
- >be used by non-windows dos programs?
-
- That would be nice, but part of the problem is that compatibility at
- the library level in DOS requires relinking an application for each
- version of the library. One would need to define, rather than just
- library calls, an ABI, or Application Binary Interface, by which the
- application can communicate with the TCP.
-
- This problem is solved in Windows by the dynamic linking Windows does
- when any program is loaded. In Windows, every system call is really
- just a library call.
-
- The big problem with developing an ABI for MS-DOS TCP is that most
- developers agree it would be great, as long as it is the ABI they
- developed for their own applications. This obviously puts everyone
- else at a disadvantage. So far, there has been only scattered support
- for a vendor-independent TCP binary interface for MS-DOS.
-
- --
- Stephen Trier "We want to offer you a price that you
- Network software type just can't afford to take advantage of."
- Case Western Reserve University - Sales blurb from HSC Software
- trier@ins.cwru.edu
-