Windows sockets

Also found in: Acronyms.

Windows sockets

(networking, standard)
(Winsock) A specification for Microsoft Windows network software, describing how applications can access network services, especially TCP/IP. Winsock is intended to provide a single API to which application developers should program and to which multiple network software vendors should conform. For any particular version of Microsoft Windows, it defines a binary interface (ABI) such that an application written to the Windows Sockets API can work with a conformant protocol implementation from any network software vendor.

Winsock was conceived at Fall Interop '91 during a Birds of a Feather session.

Windows Sockets is supported by Microsoft Windows, Windows for Workgroups, Win32s, Windows 95 and Windows NT. It will support protocols other than TCP/IP. Under Windows NT, Microsoft will provide Windows Sockets support over TCP/IP and IPX/SPX. DEC will be implementing DECNet. Windows NT will include mechanisms for multiple protocol support in Windows Sockets, both 32-bit and 16 bit.

Mark Towfiq said, "The next rev. of Winsock will not be until toward the end of 1993. We need 1.1 of the API to become firmly settled and implemented first."

Windows Sockets API. or or send a message "help" to either <ftpmail@SunSite.UNC.Edu> or <ftpmail@DECWRL.DEC.Com>.

Windows Sockets specification.

Currently NetManage (NEWT), Distinct, FTP and Frontier are shipping Winsock TCP/IP stacks, as is Microsoft (Windows NT and TCP/IP 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 TCP/IP stack vendors. Novell has one in beta for their Lan Workplace for DOS.

Peter Tattam <> is alpha-testing a shareware Windows Sockets compliant TCP/IP stack and

The Consummate Winsock App List.

[Adapted from: Aboba, Bernard D., comp.protocols.tcp-ip.ibmpc Frequently Asked Questions, 1993 Usenet: news:news.answers,].

References in periodicals archive ?
The Windows Sockets Version 2 specification will focus on three key areas.
Mark Towfiq, SunSoft's WinSock representative, and Dave Treadwell, Microsoft Corporation's Windows Sockets architect.
Recognizing that Windows Sockets has become an industry standard, application developers, end users and companies from all corners of the data communications industry have approached the Windows Sockets group asking to help make it THE preferred transport API for Microsoft Windows including Windows 3.
The Windows Sockets v2 extensions will permit these next-generation network applications to run easily over multiple transports," said David Treadwell.
Although Windows Sockets is breaking out of its TCP/IP shell, it is a goal of the WinSock v2 group to provide backwards and binary compatibility with applications written to the v1.
Blyth Software offers DAL client software for Windows and is currently developing a Windows Sockets interface for its DAL product.
Our DAL Client for Windows with Windows Sockets support will give enterprise users greater flexibility in the number of TCP/IP Windows networking solutions they can use to access their corporate data," said Philip K.
The new Windows Sockets API specification defines a standard interface between a Microsoft Windows application and a TCP/IP protocol stack.
Applications developed using NEWT-SDK Windows Sockets will be compatible with Windows Socket stacks from any other vendor.
Users and developers can now download NetManage's Windows Socket TCP/IP stack and use any application developed to this new standard.
Dan Geisler, vice president of NetMange said, "By delivering the release version of our protocol stack and Windows Socket API through immediate downloading from the Internet, we can accelerate the acceptance of the Windows Socket API.
The Windows Socket API is based on NetManage's original specifications that were submitted to the standard committee.

Full browser ?