t_connect(3N)

NAME

t_connect − establish a connection with another transport user

SYNOPSIS

cc [ flag ... ] file ... −lnsl [ library ... ]

#include <xti.h>

int t_connect(int fd, const struct t_call ∗sndcall, struct t_call ∗rcvcall);

DESCRIPTION

This routine is part of the XTI interfaces which evolved from the TLI interfaces. XTI represents the future evolution of these interfaces. However, TLI interfaces are supported for compatibility. When using a TLI routine that has the same name as an XTI routine, a different header file, tiuser.h , must be used. Refer to the section, TLI COMPATIBILITY , for a description of differences between the two interfaces.

This function enables a transport user to request a connection to the specified destination transport user. This function can only be issued in the T_IDLE state. The parameter fd identifies the local transport endpoint where communication will be established, while sndcall and rcvcall point to a t_call structure, which contains the following members:

struct netbufaddr;
struct netbufopt;
struct netbufudata;
intsequence;

sndcall specifies information needed by the transport provider to establish a connection and rcvcall specifies information that is associated with the newly established connection.

The address is specified in the netbuf structure which has the following format:

struct netbuf {
unsigned int maxlen;
unsigned int len;
char ∗buf;
}

where maxlen specifies the maximum length of the buffer in bytes, len specifies the bytes of data in the buffer, and buf points to the buffer that contains the data.

In sndcall, addr specifies the protocol address of the destination transport user, opt presents any protocol-specific information that might be needed by the transport provider, udata points to optional user data that may be passed to the destination transport user during connection establishment, and sequence has no meaning for this function.

On return, the addr field in rcvcall contains the protocol address associated with the responding transport endpoint, opt represents any protocol-specific information associated with the connection, udata points to optional user data that may be returned by the destination transport user during connection establishment, and sequence has no meaning for this function.

The opt argument permits users to define the options that may be passed to the transport provider. These options are specific to the underlying protocol of the transport provider and are described in protocol-specific documentation. The user may choose not to negotiate protocol options by setting the len field of opt to zero. In this case, the provider uses the values currently set for the communications endpoint.

If used, sndcall→opt.buf must point to a buffer with the corresponding options, and sndcall→opt.len must specify its length. the maxlen and buf fields of the netbuf structure pointed by rcvcall→addr and rcvcall→opt must be set before the call.

The udata argument enables the caller to pass user data to the destination transport user and receive user data from the destination user during connection establishment. However, the amount of user data must not exceed the limits supported by the transport provider as returned in the connect field of the info argument of t_open(3N) or t_getinfo(3N). If the len field of udata in the t_call structure referenced by sndcall is zero, no data will be sent to the destination transport user.

On return, the addr, opt, and udata fields of rcvcall will be updated to reflect values associated with the connection. Thus, the maxlen (see netbuf in t_connect()) field of each argument must be set before issuing this function to indicate the maximum size of the buffer for each. However, maxlen can be set to zero, in which case no information for this specific argument will be given to the user when t_connect() returns. If rcvcall is set to NULL , no information at all is returned.

By default, t_connect() executes in synchronous mode, and will wait for the destination user’s response before returning control to the local user. A successful return (that is, return value of zero) indicates that the requested connection has been established. However, if O_NONBLOCK is set using t_open() or fcntl(2), t_connect() executes in asynchronous mode. In this case, the call will not wait for the remote user’s response, but will return control immediately to the local user, returning −1 with t_errno set to TNODATA to indicate that the connection has not yet been established. In this way, the function simply initiates the connection establishment procedure by sending a connection request to the destination transport user.

The t_rcvconnect(3N) function is used in conjunction with t_connect() to determine the status of the requested connection.

When a synchronous t_connect() call is interrupted by the arrival of a signal, the state of the corresponding transport endpoint is T_OUTCON , allowing a further call to either t_rcvconnect(), t_rcvdis(3N), or t_snddis(3N). When an asynchronous t_connect() call is interrupted by the arrival of a signal, the state of the corresponding transport endpoint is T_IDLE .

VALID STATES

The only legitimate state (see t_getstate(3N)) for a call to this routine is T_IDLE .

RETURN VALUES

t_connect() returns:

0 On success.

−1 On failure.

On failure, t_errno is set to indicate the error, and possibly errno is set.

ERRORS

On failure, t_errno is set to one of the following:

TACCES The user does not have permission to use the specified address or options.

TADDRBUSY This transport provider does not support multiple connections with the same local and remote addresses. This error indicates that a connection already exists.

TBADADDR The specified protocol address was in an incorrect format or contained illegal information.

TBADDATA The amount of user data specified was not within the bounds allowed by the transport provider.

TBADF The specified file descriptor does not refer to a transport endpoint.

TBADOPT The specified protocol options were in an incorrect format or contained illegal information.

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. If executed in synchronous mode, the provider’s state, as seen by the user, changes to T_DATAXFER, and the information to be returned in rcvcall is discarded.

TLOOK An asynchronous event has occurred on this transport endpoint and requires immediate attention.

TNODATA O_NONBLOCK was set, so the function successfully initiated the connection establishment procedure, but did not wait for a response from the remote user.

TNOTSUPPORT This function is not supported by the underlying transport provider.

TOUTSTATE The communications endpoint referenced by fd or resfd is not in one of the states in which a call to this function is valid.

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 value.

TSYSERR A system error has occurred during execution of this function, errno will be set to the specific error.

TLI COMPATIBILITY

The XTI and TLI interface definitions have common names but use different header files. This, and other semantic differences between the two interfaces are described in the subsections below.

Interface Header

The XTI interfaces use the header file, xti.h . TLI interfaces should not use this header. They should use the header:

#include <tiuser.h>

Error Description Values

The t_errno values that can be set by the XTI interface and cannot be set by the TLI interface are:

TPROTO

TADDRBUSY

A t_errno value that this routine can return under different circumstances than its XTI counterpart is TBUFOVFLW . It can be returned even when the maxlen field of the corresponding buffer has been set to zero.

Option Buffers

The format of the options in an opt buffer is dictated by the transport provider. Unlike the XTI interface, the TLI interface does not fix the buffer format.

For more information refer to the Transport Interfaces Programming Guide.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
MT-Level	MT-Safe

Museum

Related Articles