Xref: utzoo comp.unix.questions:11519 comp.unix.wizards:14535
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Inter-machine networking on System V
Message-ID: <9598@smoke.BRL.MIL>
Date: 5 Feb 89 05:13:24 GMT
References: <446@thirdi.UUCP> <11181@ulysses.homer.nj.att.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <11181@ulysses.homer.nj.att.com> ekrell@hector.UUCP (Eduardo Krell) writes:
>You most likely want a higher level protocol than TLI provides, so
>you either write your own or, if you like TCP/IP, buy a TCP/IP driver.

Another approach is to exploit the work someone else has already done
to provide reliable high-level protocols (e.g. file transfer or remote
execution), by executing a slave process such as "remsh" to take care
of all the networking details.  Such code is FAR more portable than
code that does its own detailed connection handling, etc., and it is
general enough to deal with both AT&T and BSD styles of networking, so
one can for example have the application connect to whatever system is
desired simply by using a data table that gives the appropriate rexec
command to use for each host.  There is no loss of efficiency either,
assuming a reasonable implementation, because one gets back stream FDs
just the same as if one had done all the work the hard way.