t_rcvconnect() — Receive the confirmation from a connect request

Standards

Standards / Extensions C or C++ Dependencies
XPG4.2 both  

Format

#define _XOPEN_SOURCE_EXTENDED 1
#include <xti.h>

int t_rcvconnect(int fd, struct t_call *call);

General description

Enables a calling transport user to determine the status of a previously sent connect request. t_rcvconnect() is used in conjunction with t_connect() to establish a connection in asynchronous mode. The connection will be established on successful completion of this function.

The argument fd identifies the local transport endpoint where communication will be established, and call contains information associated with the newly established connection. The argument call points to a t_call structure which contains the following members:
        struct netbuf   addr;
        struct netbuf   opt;
        struct netbuf   udata;
        int             sequence;
In call, addr returns the protocol address associated with the responding transport endpoint. opt presents any options associated with the connection. udata is meaningless since the TCP transport provider does not support transmission of user data during connection establishment. sequence has no meaning for this function.

The maxlen field of each argument must be set before issuing this function to indicate the maximum size of the buffer for each. However, call may be a NULL pointer, in which case no information is given to the user on return from t_rcvconnect() . By default, t_rcvconnect() executes in synchronous mode and waits for the connection to be established before returning. On return, the addr field contains the address of the remote endpoint, and opt reflects the result of negotiation of the options the user specified on input.

If O_NONBLOCK is set (using t_open() or fcntl() ), t_rcvconnect() executes in asynchronous mode, and reduces to a poll for existing connect confirmations. If none are available, t_rcvconnect() fails and returns immediately without waiting for the connection to be established. (See TNODATA below.) In this case, t_rcvconnect() must be called again to complete the connection establishment phase and retrieve the information returned in call.

Valid states: T_OUTCON

Returned value

If successful, t_rcvconnect() returns 0.

If unsuccessful, t_rcvconnect() returns -1 and sets errno to one of the following values:
Error Code
Description
TBADF
The specified file descriptor does not refer to a transport endpoint.
TBUFOVFLW
The number of bytes allocated for an incoming argument (maxlen) is greater than 0 but not sufficient to store the value of that argument, and the connect information to be returned in call will be discarded. The provider's state, as seen by the user, will be changed to T_DATAXFER.
TLOOK
An asynchronous event has occurred on this transport connection and requires immediate attention.
TNODATA
O_NONBLOCK was set, but a connect confirmation has not yet arrived.
TNOTSUPPORT
This function is not supported by the underlying transport provider.
TOUTSTATE
The function was issued in the wrong sequence on the transport endpoint referenced by fd.
TPROTO
This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI (t_errno).
TSYSERR
A system error has occurred during execution of this function.

Related information