home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!netcom.com!jsbus
- From: jsbus@netcom.com (JSB Corp)
- Subject: Winsock
- Message-ID: <1992Dec23.234919.224@netcom.com>
- Summary: commercial product supports berkeley sockets and winsock
- Keywords: vsl winsock jsb
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- Date: Wed, 23 Dec 1992 23:49:19 GMT
- Lines: 22
-
- >trier@slc6.ins.cwru.edu (Stephen C. Trier) writes:
-
- Tom Wallace
- >trier@slc6.ins.cwru.edu (Stephen C. Trier) writes:
-
- >> Windows Sockets is for Windows while Berkeley Sockets is for BSD Unix.
- >> There are some significant differences caused by the different OS archi-
- >> tectures, but the spirit is meant to be the same.
- (12 lines removed)
-
- At the risk of treading into the grey area of commercial posting,
- Windows developers should note that there is a product called
- Virtual Socket Library (VSL) that uses Berkeley Sockets calls
- to talk, not only to Windows Sockets
- compliant TCP/IP's, but most of today's popular networks as well ...
- with one common API. Rather then use newsgroup space to let you
- know the details, you can contact:
-
- Tom Wallace
- tomwa@jsbus.com
- JSB Corporation - 408-438-8300 ext 209
-
-