Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!seismo!ut-sally!husc6!mit-eddie!genrad!decvax!decwrl!pyramid!prls!philabs!micomvax!ottmar
From: ottmar@micomvax.UUCP
Newsgroups: comp.bugs.sys5
Subject: AT&T Transport Interface
Message-ID: <768@micomvax.UUCP>
Date: Tue, 17-Feb-87 14:12:33 EST
Article-I.D.: micomvax.768
Posted: Tue Feb 17 14:12:33 1987
Date-Received: Thu, 19-Feb-87 21:37:47 EST
Sender: news@micomvax.UUCP
Reply-To: ottmar@micomva.UUCP (Ottmar Bochardt)
Distribution: world
Organization: Philips Information Systems Ltd., St. Laurent - Que., Canada
Lines: 20


I recently received the complete set of SVR3 documentation, and was
disappointed to find that the AT&T Transport Interface is *not*
explicitly documented.

The Network Programmer's Guide (307-230) and the SVID (307-131) both
describe only the AT&T Transport Library and not the underlying
STREAMS message formats.

Does anyone know how to obtain specifications for these messages ?
One obvious answer would be to read the library sources, but I
I don't yet have the SVR3 sources and don't know when they will arrive.

Any information would be appreciated e.g. a summary of how closely the
TI messages correspond to the transport library routines.


Ottmar Bochardt @ Philips Information Systems, Montreal

... philabs!micomvax!ottmar