Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!auspex!ntrlink!walt From: walt@ntrlink.hq.interlink.com (Walter Johnson) Newsgroups: comp.protocols.ibm Subject: Re: Interlink's TCP API Message-ID: <13574@ntrlink.hq.interlink.com> Date: 1 Apr 91 18:47:34 GMT References: <9103250530.AA24715@lilac.berkeley.edu> Reply-To: walt@ntrlink.UUCP (Walter Johnson) Organization: Interlink Computer Sciences, Inc. Lines: 22 In article <9103250530.AA24715@lilac.berkeley.edu> BITNIC IBM-NETS List writes: >4) The [Interlink] API is baroque. They modeled it after the VTAM interface The Interlink API (SNS/API) actually contains three different programming methods. The basic architecture is that defined for a Transport Interface in the OSI Reference Model. One interface provides a library of macro instruc- tions that manipulate data structures (TPLs) which are indeed modeled on VTAM RPLs. A second library provides services similar to the assembler interface, but is for programs written in C. This, too, uses the TPL data structures. Finally, a library of functions implementing a socket interface is provided for applications written in C. With this library, no knowledge of the "VTAM-like" TPL structures is required. In summary, if you like (or at least understand) VTAM, it's there for your use. If you prefer the Berkeley socket model, it too is there: it's your choice. -- Walt Johnson Business Development walt@interlink.com Interlink Computer Sciences sun!ntrlink!walt 47370 Fremont Blvd Phone (415) 657-9800 Fremont, CA 94538