*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->IRIX man pages -> ticlts (7)              
Title
Content
Arch
Section
 

Contents


ticlts(7)							     ticlts(7)


NAME    [Toc]    [Back]

     ticlts, ticots, ticotsord - loopback transport providers

SYNOPSIS    [Toc]    [Back]

     #include <ticlts.h>
     #include <ticots.h>
     #include <ticotsord.h>

DESCRIPTION    [Toc]    [Back]

     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 T_CLTS.  Its default address size is TCL_DEFAULTADDRSZ.
     ticlts prints the following error messages	(see t_rcvuderr(3N)):

	  TCL_BADADDR	   bad address specification
	  TCL_BADOPT	   bad option specification
	  TCL_NOPEER	   bound
	  TCL_PEERBADSTATE peer	in wrong state

     ticots is a virtual circuit-mode transport	provider.  It offers
     (connection-oriented) service of type T_COTS.  Its	default	address	size
     is	TCO_DEFAULTADDRSZ.  ticots prints the following	disconnect messages
     (see t_rcvdis(3N)):
	    TCO_NOPEER		    no listener	on destination address
	    TCO_PEERNOROOMONQ	    peer has no	room on	connect	queue
	    TCO_PEERBADSTATE	    peer in wrong state
	    TCO_PEERINITIATED	    peer-initiated disconnect
	    TCO_PROVIDERINITIATED   provider-initiated disconnect

     ticotsord is a virtual circuit-mode transport provider, offering service
     of	type T_COTS_ORD	(connection-oriented service with orderly release).
     Its default address size is TCOO_DEFAULTADDRSZ.  ticotsord	prints the
     following disconnect messages (see	t_rcvdis(3N)):
	    TCOO_NOPEER		     no	listener on destination	address
	    TCOO_PEERNOROOMONQ	     peer has no room on connect queue
	    TCOO_PEERBADSTATE	     peer in wrong state
	    TCOO_PEERINITIATED	     peer-initiated disconnect
	    TCOO_PROVIDERINITIATED   provider-initiated	disconnect







									Page 1






ticlts(7)							     ticlts(7)



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 (T_CLTS and T_COTS)
     supported by the OSI transport-level model. The use of ticlts and ticots
     is	encouraged.

     ticotsord supports	the same service type (T_COTSORD) supported by the
     TCP/IP model.  The	use of ticotsord is discouraged	except for reasons of
     compatibility.

FILES    [Toc]    [Back]

     /dev/ticlts
     /dev/ticots
     /dev/ticotsord


									PPPPaaaaggggeeee 2222
[ Back ]
 Similar pages
Name OS Title
ssh_externalkeys Tru64 Describes the external key providers that can be used with ssh2 software
lo FreeBSD software loopback network interface
lo OpenBSD software loopback network interface
loop FreeBSD software loopback network interface
lo Tru64 Software loopback network interface
linkloop HP-UX verify LAN connectivity with link-level loopback
mount_nullfs FreeBSD mount a loopback file system sub-tree; demonstrate the use of a null file system layer
t_sync HP-UX synchronize transport library
t_unbind HP-UX disable a transport endpoint
t_close HP-UX close a transport endpoint
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service