Lines Matching +full:application +full:- +full:dependent
9 ticlts, ticots, ticotsord \- loopback transport providers
30 ``loopback transport providers,'' that is, stand-alone networks at the
33 loopback network. Loopback transports present a \fBTPI\fR (STREAMS-level)
34 interface to application processes and are intended to be accessed via the
35 \fBTLI\fR (application-level) interface. They are implemented as clone devices
36 and support address spaces consisting of ``flex-addresses,'' that is, arbitrary
40 \fBticlts\fR is a datagram-mode transport provider. It offers (connectionless)
82 \fBticots\fR is a virtual circuit-mode transport provider. It offers
83 (connection-oriented) service of type \fBT_COTS\fR. Its default address size is
119 peer-initiated disconnect
128 provider-initiated disconnect
133 \fBticotsord\fR is a virtual circuit-mode transport provider, offering service
134 of type \fBT_COTS_ORD\fR (connection-oriented service with orderly release).
170 provider-initiated disconnect
179 peer-initiated disconnect
186 interface. Applications implemented in a transport provider-independent manner
187 on a client-server model using this \fBIPC\fR are transparently transportable
191 Transport provider-independent applications must not include the headers listed
193 transport provider options) provider dependent.
197 \fBT_COTS\fR) supported by the \fBOSI\fR transport-level model.