Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!lll-tis!lll-ati.arpa!narayan
From: narayan@lll-ati.arpa (Narayan Moharram)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: More questions about TLI
Message-ID: <21846@lll-tis.arpa>
Date: Fri, 20-Nov-87 17:31:17 EST
Article-I.D.: lll-tis.21846
Posted: Fri Nov 20 17:31:17 1987
Date-Received: Sun, 22-Nov-87 16:03:23 EST
References: <8711181601.AA00849@janeb.wisc.edu>
Sender: nobody@lll-tis.arpa
Reply-To: narayan@lll-ati.arpa (Narayan Moharram)
Organization: Lawrence Livermore National Laboratory, Livermore CA
Lines: 15

In article <8711181601.AA00849@janeb.wisc.edu> hagens@CS.WISC.EDU (Robert Hagens) writes:
>
>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


Yes it does indeed. Each read / t_recv gets you one packet only, if
the underlying protocol maintains packet boundaries (For that matter
so does the socket interface). However it is the interpretation of
urget data in TLI that bugs me.