Synonyms for winsock or Related words with winsock

netlink              netfilter              dotnet              createprocess              wininet              powershell              ipchains              ntdll              libpcap              glibc              ndis              cocreateinstance              inetd              tinyos              driverwindows              isapi              jni              jclouds              wmi              liveconnect              userland              miniport              tapi              npapi              dlopen              winpcap              umdf              iphlapi              libc              libvirt              tsapi              openssl              loadlibrary              rtai              tcpdump              cogetclassobject              getkeystate              udev              posix              minidriver              mapi              jgroups              dtrace              kmdf              mbim              idispatch              wsaioctl              inotify              nodejs              ifconfig             



Examples of "winsock"
Windows 8 includes the "RIO" (Registered IO) extensions for Winsock.
Winsock Kernel (WSK) is a new transport-independent kernel-mode Network Programming Interface (NPI) for that provides TDI client developers with a sockets-like programming model similar to those supported in user-mode Winsock. While most of the same sockets programming concepts exist as in user-mode Winsock such as socket, creation, bind, connect, accept, send and receive, "Winsock Kernel" is a completely new programming interface with unique characteristics such as asynchronous I/O that uses IRPs and event callbacks to enhance performance. TDI is supported in Windows Vista for backward compatibility.
Unlike the well-known Winsock 2 API, which is covered by numerous books, documentation, and samples, the Winsock 2 SPI is relatively unexplored. The Winsock 2 SPI is implemented by network transport service providers and namespace resolution service providers. The Winsock 2 SPI can be used to extend an existing transport service provider by implementing a Layered Service Provider. For example, Quality of Service (QoS) on Windows 98 and Windows 2000 is implemented as an LSP over the TCP/IP protocol stack. Another use for LSPs would be to develop specialized URL filtering software to prevent Web browsers from accessing certain sites, regardless of the browser installed on a desktop.
UDP Unicorn uses Winsock to create sockets and send UDP packets.
Winsock Kernel (WSK) is a new transport-independent kernel-mode Network Programming Interface (NPI) that provides TDI client developers with a sockets-like programming model similar to those supported in user-mode Winsock. While most of the same sockets programming concepts exist as in user-mode Winsock such as socket, creation, bind, connect, accept, send and receive, "Winsock Kernel" is a completely new programming interface with unique characteristics such as asynchronous I/O that uses IRPs and event callbacks to enhance performance. TDI is supported in Windows Vista for backward compatibility.
Also in 1996, OzEmail was the unsuccessful respondent in a case involving the creators of Trumpet Winsock, regarding intellectual property and trade practices matters . The court found that Sean Howard was "closely involved in all stages of the project". At the time this distribution occurred in 1995, Trumpet Winsock 2.0B was commonly distributed by ISPs without properly licensing it. The lawsuit alleged that OzEmail deliberately removed reference to the fact that it was shareware and required registration. Trumpet Winsock 2.1 was the first timelocked version, released in July 1995. This was too late for OzEmail, which went ahead and distributed the 2.0B version without permission, before 2.1 was released, but it did have a draft README mentioning that the new version would be time-locked to 30 days and then need to be registered. That was also just before Windows 95 was released, which has built-in TCP/IP support. Trumpet Winsock 2.1 would not work with Win32 Winsock applications.
The command "netsh winsock reset" can be used to reset TCP/IP problems when communicating with a networked device.
MS MPI can use any physical network, including Gigabit ethernet, Infiniband and Myrinet, for which a Winsock Direct driver has been provided. The Winsock Direct provider bypasses the TCP/IP stack of the OS and directly provides access to the networking hardware, using transport protocols tailored for the network type. In absence of such drivers, the TCP/IP stack can also be used.
SuperSockets is a software infrastructure for Dolphin Express providing a very low latency, high throughput implementation of the Berkeley sockets and Winsock APIs.
Scott Swedorski is the founder of Tucows (The Ultimate Collection of Winsock Software), a large Internet domain name reseller, and Internet service provider.
This protocol has been deprecated or not maintained by OFED in the latest releases, hence look for alternatives. The probable suggestions will be RSOCKET, WINSOCK, etc.
Layered Service Provider (LSP) is a deprecated feature of the Microsoft Windows Winsock 2 Service Provider Interface (SPI). A Layered Service Provider is a DLL that uses Winsock APIs to attempt to insert itself into the TCP/IP protocol stack. Once in the stack, a Layered Service Provider can intercept and modify inbound and outbound Internet traffic. It allows processing of all the TCP/IP traffic taking place between the Internet and the applications that are accessing the Internet (such as a web browser, the email client, etc.). For example, it could be used by malware to redirect web browers to rogue websites, or to block access to sites like Windows Update. Alternatively, a computer security program could scan network traffic for viruses or other threats. The Winsock "Service Provider Interface (SPI)" API provides a mechanism for layering providers on top of each other. Winsock LSPs are available for a range of useful purposes, including parental controls and Web content filtering. The parental controls web filter in Windows Vista is an LSP. The layering order of all providers is kept in the Winsock Catalog.
In 2005, Wong co-founded Karmasphere.com with Martin Hall, the inventor of WinSock. Karmasphere.com aims to offer the second half: reputation. Wong has described Karmasphere as "the credit bureau for Internet identities".
A feature of LSP and Winsock proxy sniffing is that they allow traffic to be captured from a single application and also enable traffic going to localhost (127.0.0.1) to be sniffed on Windows.
All modern operating systems implement a version of the Berkeley or POSIX socket interface. It became the standard interface for connecting to the Internet. Even the Winsock implementation for MS Windows, developed by unaffiliated developers, closely follows the standard.
Solaris 10 and Solaris 11 Express include support for SDP. Several other Unix operating system variants plan to include support for Sockets Direct Protocol. Windows offers a subsystem called Winsock Direct, which could be used to support SDP.
WS2_32.DLL implements the Winsock API, which provides TCP/IP networking functions and provides partial, broken compatibility with other network APIs. wsock.dll and wsock32.dll are older versions for Win3.11 and Win95 compatibility.
Winsock 2 LSPs are implemented as Windows DLLs with a single exported entry function, "WSPStartup". All other transport SPI functions are made accessible to ws2_32.dll or an upper chain layered provider via the LSP's dispatch table. LSPs and base providers are strung together to form a protocol chain. The LSP DLL has to be registered using a special LSP registrant which instructs Winsock 2, the loading order of the LSPs (there can be more than one LSP installed) and which protocols to intercept.
For example, Microsoft Windows' Winsock, and Unix's Berkeley sockets and System V Transport Layer Interface, are interfaces between applications (layer 5 and above) and the transport (layer 4). NDIS and ODI are interfaces between the media (layer 2) and the network protocol (layer 3).
Such potential loss of all network connectivity is prevented in Windows XP Service Pack 2, Windows Server 2003 Service Pack 1 and all later Windows operating systems, in which Winsock has the ability to self-heal after a user uninstalls such an LSP.