NAME

t_accept, t_alloc, t_bind, t_close, t_connect, t_error,t_free,t_getinfo, t_getstate, t_listen, t_look, t_open, t_optmgmt, t_rcv, t_rcvconnect, t_rcvdis, t_rcvrel, t_rcvudata, t_rcvuderr, t_snd, t_snddis, t_sndrel, t_sndudata, t_sync, t_unbind − X/Open Transport Interface Library

SYNOPSIS

#include <xti.h>

int t_accept(fd, resfd, call)
int fd, resfd;
struct t_call ∗call;

char ∗t_alloc(fd, type, fields)
int fd, type, fields;

int t_bind(fd, req, ret)
int fd;
struct t_bind ∗req, ∗ret;

int t_close(fd)
int fd;

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

int t_error(errmsg)
char ∗errmsg;

int t_free(ptr, type)
char ∗ptr;
int type;

int t_getinfo(fd, info)
int fd;
struct t_info ∗info;

int t_getstate(fd)
int fd;

int t_listen(fd, call)
int fd;
struct t_call ∗call;

int t_look(fd)
int fd;

int t_open(name, oflag, info)
char ∗name;
int oflag;
struct t_info ∗info;

int t_optmgmt(fd, req, ret)
int fd;
struct t_optmgmt ∗req, ∗ret;

int t_rcv(fd, buf, nbytes, flags)
int fd;
char ∗buf;
unsigned nbytes;
int ∗flags;

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

int t_rcvdis(fd, discon)
int fd;
struct t_discon ∗discon;

int t_rcvrel(fd)
int fd;

int t_rcvudata(fd, unitdata, flags)
int fd;
struct t_unitdata ∗unitdata;
int ∗flags;

int t_rcvuderr(fd, uderr)
int fd;
struct t_uderr ∗uderr;

int t_snd(fd, buf, nbytes, flags)
int fd;
char ∗buf;
unsigned nbytes;
int ∗flags;

int t_snddis(fd, call)
int fd;
struct t_call ∗call;

int t_sndrel(fd)
int fd;

int t_sndudata(fd, unitdata)
int fd;
struct t_unitdata ∗unitdata;

int t_sync(fd)
int fd;

int t_unbind(fd)
int fd;

DESCRIPTION

The XTI routines implement the Transport Interface library as defined by the X/Open Portability Guide,  Networking Services publication. XTI defines a transport service interface which is independent of any specific provider.  It is functionally compatible with the AT&T Transport Level Interface as defined by the System V Interface Definition (SVID). 

XTI consists of a series of library functions providing access to networking services.  The library routines are not dependent upon the kernel implementation.  However, they are typically implemented along with a STREAMS-based networking system.  The CX/UX XTI library is built on top of the CX/UX sockets-based networking system.  This difference is generally transparent to the caller. 

Protocols accessible through the XTI under CX/UX include tcp/ip, udp, and icmp.  These Internet protocols can only support a subset of the full XTI capabilities.  This subset can be found in the X/Open document listed below. 

FILES

usr/lib/libxti.a

SEE ALSO

X/Open Portability Guide, Networking Services

CX/UX Networking