NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/protocol/tcpip/ibmpc/7683

Internet Message Format | 1993-01-25 | 1.6 KB

Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!netman-gate.netmanage.com!boris
From: [e-mail] (Boris Yanovsky)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: RE: .uk
Message-ID: <[e-mail]>
Date: 25 Jan 93 17:29:44 GMT
Sender: [e-mail]
Reply-To: [e-mail]
Distribution: world
Organization: The Internet
Lines: 28

>I'm pleased that the Windows Sockets thing is starting to pick up, but is
>anyone actually in the process of writing a freely available winsock.dll ?
>Maybe Microsoft are going to start distributing one with Windows itself.
>Surely this would save confusion? Although, of course, vendors should be able
>to create thier own also, as they may be better tuned.

The reason for doing Windows Sockets was to provide a single interface for
different vendors transports (originaly each vendor had his own interface).
To provide a single DLL wich can access each individual vendors transport is a
large job which now becomes unnecessary.  When you purchase a TCP/IP product it
should have a Windows Socket interface built in, so even though you are geting a
winsock.dll as a separate file it is part of the product.

I guess what I am trying to stress that winsock.dll is NOT a separate product.
The products is the TCP/IP (hopefully in the future any transport) stack with
Windows Sockets API.


***************************************
Boris Yanovsky
20823 Stevens Creek Blvd., Suite 100
Cupertino, CA 95014
phone: [phone]
fax:   [phone]
[e-mail]
***************************************