Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!CSL.SRI.COM!AUERBACH
From: AUERBACH@CSL.SRI.COM (Karl Auerbach)
Newsgroups: comp.protocols.tcp-ip
Subject: STREAM, TLI, and (of all things) MAP 3.0
Message-ID: <8707310111.AA28460@ucbvax.Berkeley.EDU>
Date: Thu, 30-Jul-87 21:07:20 EDT
Article-I.D.: ucbvax.8707310111.AA28460
Posted: Thu Jul 30 21:07:20 1987
Date-Received: Sat, 1-Aug-87 11:54:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 17

I was wondering whether TLI (Transport Level Interface) is an intrinsic
part of STREAMS?  If severable, is TLI required by AT&T?

Can TLI support fully asynchronous operations.  In other words can
I initiate a bunch of connects, sends, listens, receives.., continue
running and get some sort of call-back, up-call, AST (pick your favorite
name) when something completes?

If TLI is an ISO transport interface, who provides graceful close?  (ISO
transport does not have graceful close, that's part of session.)

I have on my desk a copy of a working document from the GM MAP 3.x folks.
It defines a programmatic interface for applications.  If anyone is familiar
with that and TLI, I'd like to hear your comments.

			--karl--
-------