Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!ucbcad!ucbvax!CS.WISC.EDU!hagens
From: hagens@CS.WISC.EDU (Robert Hagens)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: More questions about TLI
Message-ID: <8711181601.AA00849@janeb.wisc.edu>
Date: Wed, 18-Nov-87 11:01:31 EST
Article-I.D.: janeb.8711181601.AA00849
Posted: Wed Nov 18 11:01:31 1987
Date-Received: Sat, 21-Nov-87 10:32:03 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16

Bill Crews writes about TLI:

> One reason it might be better is that it makes no assumptions about the
> underlying protocols -- or, I should say, minimal assumptions.  For instance,
> connection-oriented service, a "byte-stream" mode is supported.  Some
> underlying protocols may allow preservation of message boundaries and some may
> not.  The application programmer can maintain portability by refraining from
> making that assumption.  Nothing in TLI forces that assumption.

Does TLI allow one to take advantage of the message boundaries? ISO session
depends on the message boundaries provided by ISO transport. If it does not,
you may find yourself in trouble when you try to support an OSI stack.

Rob Hagens
UW Madison Computer Science
ARGO project