s = socket(AF_UNIX, SOCK_STREAM, 0);
t = t_open("/dev/ticots", O_RDWR, infop);
In the synopsis, s and t are file descriptors for the respective endpoints on calls to functions opening a file descriptor for a transport endpoint.
/dev/ticots is typically invoked as the implied device in a call to socket or as the first argument in a call to t_open and is used to identify the transport protocol that will supply a connection-based transport service.
The device known as /dev/ticots is a ``loopback transport provider,'' that is, a stand-alone network at the transport level. Loopback devices are transport providers in every sense except one: only one host (the local machine) is ``connected to'' a loopback network.
/dev/ticots may be used as a clone device to find a minor available device for the transport user. It presents a TPI (STREAMS-level) interface to application processes and is intended to be accessed via the TLI or socket (application-level) interface. It supports address spaces consisting of ``flex-addresses,'' that is, arbitrary sequences of octets, of length > 0, represented by a netbuf structure, described in intro(3xti).
/dev/ticots supports the same service type (T_COTS) supported by the OSI transport-level model and its use is encouraged.