ticlts(7) ticlts(7)
NAME
ticlts, ticots, ticotsord - loopback transport providers
SYNOPSIS
#include <ticlts.h>
#include <ticots.h>
#include <ticotsord.h>
DESCRIPTION
The devices known as ticlts, ticots, and ticotsord are ``loopback
transport providers,'' that is, stand-alone networks at the transport
level. Loopback transport providers are transport providers in every
sense except one: only one host (the local machine) is ``connected
to'' a loopback network. Loopback transports present a TPI
(STREAMS-level) interface to application processes and are intended
to be accessed via the TLI (application-level) interface. They are
implemented as clone devices and support address spaces consisting of
``flex-addresses,'' i.e., arbitrary sequences of octets, of length
> 0, represented by a netbuf structure.
ticlts is a datagram-mode transport provider. It offers
(connectionless) service of type TCLTS. Its default address size is
TCLDEFAULTADDRSZ. ticlts prints the following error messages (see
trcvuderr(3N)):
TCLBADADDR bad address specification
TCLBADOPT bad option specification
TCLNOPEER bound
TCLPEERBADSTATE peer in wrong state
ticots is a virtual circuit-mode transport provider. It offers
(connection-oriented) service of type TCOTS. Its default address
size is TCODEFAULTADDRSZ. ticots prints the following disconnect
messages (see trcvdis(3N)):
TCONOPEER no listener on destination address
TCOPEERNOROOMONQ peer has no room on connect queue
TCOPEERBADSTATE peer in wrong state
TCOPEERINITIATED peer-initiated disconnect
TCOPROVIDERINITIATED provider-initiated disconnect
ticotsord is a virtual circuit-mode transport provider, offering
service of type TCOTSORD (connection-oriented service with orderly
release). Its default address size is TCOODEFAULTADDRSZ. ticotsord
prints the following disconnect messages (see trcvdis(3N)):
8/91 Page 1
ticlts(7) ticlts(7)
TCOONOPEER no listener on destination address
TCOOPEERNOROOMONQ peer has no room on connect queue
TCOOPEERBADSTATE peer in wrong state
TCOOPEERINITIATED peer-initiated disconnect
TCOOPROVIDERINITIATED provider-initiated disconnect
USAGE
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.
ticlts and ticots support the same service types (TCLTS and TCOTS)
supported by the OSI transport-level model. The use of ticlts and
ticots is encouraged.
ticotsord supports the same service type (TCOTSORD) supported by the
TCP/IP model. The use of ticotsord is discouraged except for reasons
of compatibility.
FILES
/dev/ticlts
/dev/ticots
/dev/ticotsord
Page 2 8/91