home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!microsoft!hexnut!alistair
- From: alistair@microsoft.com (Alistair Banks)
- Subject: Re: Windows Socket API
- Message-ID: <1992Aug24.180413.4370@microsoft.com>
- Date: 24 Aug 92 18:04:13 GMT
- Organization: Microsoft Corporation
- References: <RAF@CU.NIH.GOV> <9208210943.aa03735@louie.udel.edu> <1592@anagld.analytics.com>
- Lines: 25
-
- In article <1592@anagld.analytics.com> sammy@anagld.analytics.com (Sam Blackburn) writes:
- >PIRARD@VM1.ULG.AC.BE (Andre' PIRARD) writes:
- >
- >>On Thu, 11 Jun 1992 00:34:41 EDT Roger Fajman said:
- >>>The Windows Socket API sounds like a big step forward. I wish that
- >>>it dealt with DOS applications too, however.
- >
- >I just ordered the TCP/IP SDK from Microsoft and the salesman said that it
- >covers Windows, DOS and OS/2 (probably 1.3). This is the SDK that implements
- >WinSock API.
-
- Sadly, this isn't right. The kit you were offerrred implements a sockets API
- for ms-dos, windows & os/2, but it isn't yet "Windows Sockets" compliant.
-
- Our "Preliminary Win32 SDK for Windows NT" implements Win16 & Win32 APIs
- compliant with the "Windows Sockets" standard, but both implementations are
- for use in Windows NT - we're working on Windows 3.x "Windows Sockets" i/f,
- but haven't completed that yet, and have nothing to announce today.
-
- If you remember, please give me the name of the salesman and I will give
- him the correct information. This is a very esoteric area, and
- its hard to explain that a sockets lib for Windows is not always "Windows
- Sockets" compliant. Things should get simpler as a few implementations
- hit the market - I'm hoping fall Interop related demonstrations will
- sort things out -- Alistair
-