ticots(7)                        DG/UX R4.11                       ticots(7)


NAME
       ticots - connection-oriented loopback transport provider

SYNOPSIS
       #include <tiuser.h>

       t = topen("/dev/ticots", ORDWR);

DESCRIPTION
       ticots is a connection-mode transport provider offering service of
       type TCOTS.

       In the synopsis, t is a file descriptor for the endpoint on calls to
       functions opening a file descriptor for a transport endpoint.

       /dev/ticots is typically invoked as the first argument in a call to
       topen and is used to identify the transport protocol that will
       supply a connectionless transport service.

       The device known as ticots is a ``loopback transport provider,'' that
       is, a stand-alone network at the transport level.  Loopback providers
       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 (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(3).

   Return Values
       The value returned by a call to open an endpoint with /dev/ticots is
       a file descriptor characterizing the endpoint.

FILES
       /dev/ticots                   ticots driver device node.
       /usr/include/sys/ticots.h     Error return definitions.

SEE ALSO
       intro(3), socket(3N), topen(3N), trcvdis(3N), clone(7), ticlts(7),
       ticotsord(7).

NOTES
       Loopback transports support a local IPC mechanism through the TLI
       interface.  Applications implemented in a transport provider-
       independent manner on a client-server model using this IPC are
       transparently transportable to networked environments.

       Transport provider-independent applications must not include the
       header files listed in the synopsis section above.  In particular,
       the options are (like all transport provider options) provider
       dependent.


Licensed material--property of copyright holder(s)