Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!uwvax!oddjob!hao!ames!oliveb!sun!gorodish!guy
From: guy%gorodish@Sun.COM (Guy Harris)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: Streams TCP/IP
Message-ID: <24072@sun.uucp>
Date: Thu, 23-Jul-87 14:39:41 EDT
Article-I.D.: sun.24072
Posted: Thu Jul 23 14:39:41 1987
Date-Received: Sat, 25-Jul-87 08:42:07 EDT
References: <725@hjuxa.UUCP> <649@houxa.UUCP> <278@unixprt.UUCP>
Sender: news@sun.uucp
Lines: 21
Keywords: TCP/IP, Streams
Xref: mnetor comp.dcom.lans:681 comp.protocols.tcp-ip:679

> The primary advantage, for those using ATT based UNIX, is that this is the
> only 'real' facility provided in UNIX System V to support networking.

Gee, for some time now the people at Berkeley have been using an
"AT&T-based UNIX" (the only non-"AT&T-based" UNIXes I know of are
things like Mark Williams' "Coherent", which was written from
scratch) that supports networking without STREAMS.  Plenty of other
people have dropped the socket code into System V kernels, just as
Berkeley dropped it into a 32V-derived kernel, so STREAMS are not
"the only game in town".

> ATT's Transport Interface is mostly base on the ISO transport interface,
> therefore should map to the emerging interface standards.

Unfortunately, the TLI also has a number of warts, such as the fact
that it keeps some state both in userland and in the kernel, so that
after a "fork"/"exec" you have to issue a "t_sync" call to pull the
kernel's notion of the state into userland.
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com