Accepts a pending connection request and assigns an endpoint to use in the data exchange.
HRESULT Accept( [in] INDEndpoint *pEndpoint, [in, optional] const VOID *pPrivateData, [in] SIZE_T PrivateDataLength, [in, out] OVERLAPPED *pOverlapped );
An INDEndpoint interface that defines the endpoint to connect to the peer's endpoint. The endpoint must have been created using this instance of the Connector object.
pPrivateData [in, optional]
Private data to transmit to the peer. Can be NULL if PrivateDataLength is zero.
The size, in bytes, of the pPrivateData buffer.
pOverlapped [in, out]
A pointer to an OVERLAPPED structure that is used to indicate completion of the operation.
When you implement this method, you should return the following return values. If you return others, try to use well-known values to aid in debugging issues.
The operation succeeded.
The request is pending and will be completed when the connection is fully established.
The endpoint was removed.
The underlying Network Direct adapter was removed from the system.
The specified endpoint is already connected.
The connecting peer aborted the connection establishment.
The pPrivateData buffer is not valid for the size specified in PrivateDataLength.
The peer did not call the INDConnector::CompleteConnect method to complete the connection.
Calling this method causes the peer's connection request to complete.
An endpoint can be connected to only one other endpoint at a time.
The inbound and outbound read limits that you specify in the endpoint object are the limits that will be used for the connection. The connecting peer calls the INDConnector::GetConnectionData to get the limits and determines if the limits are acceptable. If the limits are acceptable, the connecting peer calls the INDConnector::CompleteConnect method; otherwise, the peer calls the INDConnector::Reject method to cancel the connection.
|Microsoft Message Passing Interface (MS-MPI)|
Build date: 7/2/2010