| Windows sockets (Winsock) A specification for network software, describing how applications can access network services, especially . Winsock is intended to provide a single to which application developers should program and to which multiple network software vendors should conform. For any particular version of , it defines a binary interface () such that an application written to the Windows Sockets API can work with a conformant implementation from any network software vendor. Winsock was conceived at Fall Interop '91 during a session. Windows Sockets is supported by , , , and . It will support protocols other than . Under , will provide Windows Sockets support over and /. will be implementing . will include mechanisms for multiple support in Windows Sockets, both 32-bit and 16 bit. Mark Towfiq said, "The next rev. of Winsock will not be until towards the end of 1993. We need 1.1 of the to become firmly settled and implemented first." {Windows Sockets API (ftp://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock)} or {(ftp://microdyne.com/pub/winsock)} or send a message "help" to either or . {Windows Sockets specification (ftp://rhino.microsoft.com)} Currently NetManage (NEWT), Distinct, FTP and Frontier are shipping Winsock stacks, as is (Windows NT and for WFW), Beame & Whiteside Software (v1.1 compliant), and Sun PC-NFS. Windows 95 has "dial-up networking" which supports Winsock and TCP/IP. winsock.dll is available from some stack vendors. has one in beta for their for . Peter Tattam is alpha-testing a shareware Windows Sockets compliant stack {(ftp://ftp.utas.edu.au/pc/trumpet/winsock/winsock.zip)} and {(ftp://ftp.utas.edu.au/pc/trumpet/winsock/winpkt.com)}. {The Consummate Winsock App List (http://wwwvms.utexas.edu/~Neuroses/cwsapps.html)}. [Adapted from: Aboba, Bernard D., comp.protocols.tcp-ip.ibmpc Frequently Asked Questions, 1993 : {news:news.answers}, {(ftp://netcom1.netcom.com/pub/mailcom/IBMTCP/)}]. [Current status?] (1996-06-20) |
на заглавную 
к началу страницы