The WSPConnect function establishes a connection to a peer, exchanges connect data, and specifies needed quality of service based on the supplied flow specification.
int WSPConnect (
SOCKET s,
const struct sockaddr FAR * name,
int namelen,
LPWSABUF lpCallerData,
LPWSABUF lpCalleeData,
LPQOS lpSQOS,
LPQOS lpGQOS,
LPINT lpErrno
);
This function is used to create a connection to the specified destination, and to perform a number of other ancillary operations that occur at connect time as well. If the socket, s, is unbound, unique values are assigned to the local association by the system, and the socket is marked as bound.
For connection-oriented sockets (for example, type SOCK_STREAM), an active connection is initiated to the specified host using name (an address in the name space of the socket; for a detailed description, please see WSPBind). When this call completes successfully, the socket is ready to send/receive data. If the address field of the name structure is all zeroes, WSPConnect will return the error WSAEADDRNOTAVAIL. Any attempt to re-connect an active connection will fail with the error code WSAEISCONN.
For connection-oriented, nonblocking sockets it is often not possible to complete the connection immediately. In such a case, this function returns with the error WSAEWOULDBLOCK but the operation proceeds. When the success or failure outcome becomes known, it may be reported in one of several ways depending on how the client registers for notification. If the client uses WSPSelect success is reported in the writefds set and failure is reported in the exceptfds set. If the client uses WSPAsyncSelect or WSPEventSelect, the notification is announced with FD_CONNECT and the error code associated with the FD_CONNECT indicates either success or a specific reason for failure.
For a connectionless socket (for example, type SOCK_DGRAM), the operation performed by WSPConnect is to establish a default destination address so that the socket can be used with subsequent connection-oriented send and receive operations (WSPSend,WSPRecv). Any datagrams received from an address other than the destination address specified will be discarded. If the address field of the name structure is all zeroes, the socket will be "dis-connected" — the default remote address will be indeterminate, so WSPSend and WSPRecv calls will return the error code WSAENOTCONN, although WSPSendTo and WSPRecvFrom can still be used. The default destination can be changed by simply calling WSPConnect again, even if the socket is already "connected". Any datagrams queued for receipt are discarded if name is different from the previous WSPConnect.
For connectionless sockets, name can indicate any valid address, including a broadcast address. However, to connect to a broadcast address, a socket must have WSPSetSockOpt SO_BROADCAST enabled. Otherwise, WSPConnect will fail with the error code WSAEACCES.
On connectionless sockets, exchange of user to user data is not possible and the corresponding parameters will be silently ignored.
The Windows Sockets SPI client is responsible for allocating any memory space pointed to directly or indirectly by any of the parameters it specifies.
The lpCallerData is a value parameter which contains any user data that is to be sent along with the connection request. If lpCallerData is NULL, no user data will be passed to the peer. The lpCalleeData is a result parameter which will reference any user data passed back from the peer as part of the connection establishment. lpCalleeData->len initially contains the length of the buffer allocated by the Windows Sockets SPI client and pointed to by lpCalleeData->buf. lpCalleeData->len will be set to zero if no user data has been passed back. The lpCalleeData information will be valid when the connection operation is complete. For blocking sockets, this will be when the WSPConnect function returns. For nonblocking sockets, this will be after the FD_CONNECT notification has occurred. If lpCalleeData is NULL, no user data will be passed back. The exact format of the user data is specific to the address family to which the socket belongs and/or the applications involved.
At connect time, a Windows Sockets SPI client can use the lpSQOS and/or lpGQOS parameters to override any previous QOS specification made for the socket through WSPIoctl with either the SIO_SET_QOS or SIO_SET_GROUP_QOS opcodes.
lpSQOS specifies the flow specifications for socket s, one for each direction, followed by any additional provider-specific parameters. If either the associated transport provider in general or the specific type of socket in particular cannot honor the QOS request, an error will be returned as indicated below. The sending or receiving flow specification values will be ignored, respectively, for any unidirectional sockets. If no provider-specific parameters are supplied, the buf and len fields of lpSQOS->ProviderSpecific should be set to NULL and zero, respectively. A NULL value for lpSQOS indicates no application supplied QOS.
Reserved for future use with socket groups: lpGQOS specifies the flow specifications for the socket group (if applicable), one for each direction, followed by any additional provider-specific parameters. If no provider-specific parameters are supplied, the buf and len fields of lpGQOS->ProviderSpecific should be set to NULL and zero, respectively. A NULL value for lpGQOS indicates no application-supplied group QOS. This parameter will be ignored if s is not the creator of the socket group.
When connected sockets break (that is, become closed for whatever reason), they should be discarded and recreated. It is safest to assume that when things go awry for any reason on a connected socket, the Windows Sockets SPI client must discard and recreate the needed sockets in order to return to a stable point.
If no error occurs, WSPConnect returns zero. Otherwise, it returns SOCKET_ERROR, and a specific error code is available in lpErrno.
On a blocking socket, the return value indicates success or failure of the connection attempt. If the return error code indicates the connection attempt failed (that is, WSAECONNREFUSED, WSAENETUNREACH, WSAETIMEDOUT) the Windows Sockets SPI client can call WSPConnect again for the same socket.
| WSAENETDOWN | The network subsystem has failed. |
| WSAEADDRINUSE | The local address of the socket is already in use and the socket was not marked to allow address reuse with SO_REUSEADDR. This error usually occurs at the time of bind, but could be delayed until this function if the bind was to a partially wild-card address (involving ADDR_ANY) and if a specific address needs to be "committed" at the time of this function.. |
| WSAEINTR | The (blocking) call was canceled through WSPCancelBlockingCall. |
| WSAEINPROGRESS | A blocking Windows Sockets call is in progress, or the service provider is still processing a callback function. |
| WSAEALREADY | A nonblocking WSPConnect call is in progress on the specified socket. In order to preserve backward compatibility, this error is reported as WSAEINVAL to Windows Sockets 1.1 applications that link to either WINSOCK.DLL or WSOCK32.DLL |
| WSAEADDRNOTAVAIL | The remote address is not a valid address (for example, ADDR_ANY). |
| WSAEAFNOSUPPORT | Addresses in the specified family cannot be used with this socket. |
| WSAECONNREFUSED | The attempt to connect was rejected. |
| WSAEFAULT | The name or the namelen argument is not a valid part of the user address space, the namelen argument is too small, the buffer length for lpCalleeData, lpSQOS, and lpGQOS are too small, or the buffer length for lpCallerData is too large. |
| WSAEINVAL | The parameter s is a listening socket, or the destination address specified is not consistent with that of the constrained group the socket belongs to. |
| WSAEISCONN | The socket is already connected (connection-oriented sockets only). |
| WSAENETUNREACH | The network cannot be reached from this host at this time. |
| WSAENOBUFS | No buffer space is available. The socket cannot be connected. |
| WSAENOTSOCK | The descriptor is not a socket. |
| WSAEOPNOTSUPP | The flow specifications specified in lpSQOS and lpGQOS cannot be satisfied. |
| WSAEPROTONOSUPPORT | The lpCallerData augment is not supported by the service provider. |
| WSAETIMEDOUT | Attempt to connect timed out without establishing a connection. |
| WSAEWOULDBLOCK | The socket is marked as nonblocking and the connection cannot be completed immediately. It is possible to WSPSelect the socket while it is connecting by WSPSelecting it for writing. |
| WSAEACCES | Attempt to connect datagram socket to broadcast address failed because WSPSetSockOpt SO_BROADCAST is not enabled. |
Windows NT: Yes
Windows: Yes
Windows CE: Unsupported.
Header: Declared in ws2spi.h.
WSPAccept, WSPBind, WSPGetSockName, WSPGetSockOpt, WSPSocket, WSPSelect, WSPEventSelect, WSPEnumNetworkEvents