A connection to another socket is created with a connect call. Once connected, data can be transferred using send and recv calls. When a session has been completed, a closesocket must be performed. The communications protocols used to implement a reliable, connection-oriented socket ensure that data is not lost or duplicated.
Connectionless, message-oriented sockets allow sending and receiving of datagrams to and from arbitrary peers using sendto and recvfrom. If such a socket is connected to a specific peer, datagrams can be sent to that peer using send and can be received only from this peer using recv. The IPv6 receive packet includes the packet payload and the next upper-level header. The IPv6 receive packet never includes the IPv6 packet header.
On Windows XP and later, the following command can be used to list the Windows Sockets catalog to determine the service providers installed and the address family, socket type, and protocols that are supported.
Windows 8. Reliable Multicast Programming. Winsock Functions. Winsock Reference. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Windows Sockets 2 Winsock enables programmers to create advanced Internet, intranet, and other network-capable applications to transmit application data across the wire, independent of the network protocol being used.
It was later adapted for Windows in Windows Sockets 1. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. The ideal value for the amount of data outstanding to achieve the best throughput for the TCP connection is called the ideal send backlog ISB size. The ISB value is a function of the bandwidth-delay product of the TCP connection and the receiver's advertised receive window and partly the amount of congestion in the network.
Enables or disables the per-connection setting of the TCP keep-alive option which specifies the TCP keep-alive timeout and interval. For more information on the keep-alive option, see section 4. This resource may only be available in English. The keep-alive timeout specifies the timeout, in milliseconds, with no activity until the first keep-alive packet is sent. The keep-alive interval specifies the interval, in milliseconds, between when successive keep-alive packets are sent if no acknowledgement is received.
Configures a TCP socket for lower latency and faster operations on the loopback interface. Controls whether data sent by an application on the local computer not necessarily by the same socket in a multicast session will be received by a socket joined to the multicast destination group on the loopback interface.
A value of TRUE causes multicast data sent by an application on the local computer to be delivered to a listening socket on the loopback interface. A value of FALSE prevents multicast data sent by an application on the local computer from being delivered to a listening socket on the loopback interface. Specifies the scope over which multicast transmissions will occur.
Scope is defined as the number of routed network segments to be covered. A scope of zero would indicate that the multicast transmission would not be placed on the wire but could be disseminated across sockets within the local host. A scope value of one the default indicates that the transmission will be placed on the wire, but will not cross any routers.
Higher scope values determine the number of routers that can be crossed. By default, scope is 1. Queries offload interfaces for receive-side scaling RSS capability. This structure is defined as follows:. In high-speed networking where multiple CPUs reside within a single system, the ability of the networking protocol stack to scale well on a multi-CPU system is inhibited because the architecture of NDIS 5. Receive-side scaling RSS resolves this issue by allowing the network load from a network adapter to be balanced across multiple CPUs.
Queries the transport settings on a socket. On Windows Server , however, there are edge firewall implementations which would like to leverage the WFP platform to inspect and proxy pass-through traffic. There are some firewall scenarios that may require the ability to inject an inbound packet into the send path associated with an existing endpoint.
There needs to be a mechanism to discover the transport layer endpoint handle associated with the destination endpoint. The application that created the endpoint owns these transport layer endpoints. This WFP feature facilitates tracking of redirection records from the initial redirect of a connection to the final connection to the destination.
Enables a socket to receive all IPv4 or IPv6 packets passing throuigh a network interface. The socket handle passed to the WSAIoctl function must be one of the following:. On Windows 7 and Windows Server R2 , this was changed so that local packets sent out of a network interface are also captured.
Note that you must supply a sufficiently large buffer. Enables a socket to receive all multicast IP traffic on the network that is, all IP packets destined for IP addresses in the range of The socket should bind to port zero. To receive notification of a routing interface change that should be used to reach the remote address in the input buffer specified as a sockaddr structure. It is recognized that routing information remains stable in most cases so that requiring the application to keep multiple outstanding IOCTLs to get notifications about all destinations that it is interested in as well as having the service provider keep track of these notification requests will use a significant amount system resources.
This situation can be avoided by extending the meaning of the input parameters and relaxing the service provider requirements as follows:. To obtain the address of the local interface represented as sockaddr structure which should be used to send to the remote address specified in the input buffer as sockaddr.
Remote multicast addresses may be submitted in the input buffer to get the address of the preferred interface for multicast transmission.
In any case, the interface address returned may be used by the application in a subsequent bind request. Note that routes are subject to change.
0コメント