home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!cc.usu.edu!jrd
- From: jrd@cc.usu.edu (Joe Doupnik)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: .uk
- Message-ID: <1993Jan23.171038.63092@cc.usu.edu>
- Date: 23 Jan 93 17:10:38 MDT
- References: <memo.889132@cix.compulink.co.uk>
- Organization: Utah State University
- Lines: 17
-
- In article <memo.889132@cix.compulink.co.uk>, steveb@cix.compulink.co.uk
- (Steve Browne) writes:
- > 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.
- >
- > Steve Browne
- > PC Mag UK
- ----------------
- Slowly now Steve. Let's say external TCP/IP stacks are all different,
- which is telling the truth. Thus the .DLL has to speak to each stack in the
- way that stack prefers, and that yields the simple conclusion of no free stack
- means no free winsock.dll. Each commercial vendor will probably offer their
- own .DLL.
- Joe D.
-