Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Are sockets the wave of the future?
Message-ID: <3980@auspex.auspex.com>
Date: 29 Aug 90 21:04:25 GMT
References: <9008281330.AA00189@atlantic.nprdc.navy.mil>
Organization: Auspex Systems, Santa Clara
Lines: 16

>RPC seems suitable for networking your application if your application
>can be implemented using function call/return.  It doesn't seem suitable
>for networking your application if your application simply blasts a variable
>(and perhaps voluble) amount of text to the user's screen (or into a file).

Actually, there is an application I use that uses RPC to blast variable
amounts of text into a file; it's the UNIX copy program.  Since my
machine is diskless, any such copies go over NFS, which runs atop
RPC....

This does, of course, involve more than just the RPC code; it also
involves code that sits atop RPC, including code that turns "read()"s
and "write()"s into the NFS requests sent over RPC.  As such, you might
have to write similar stuff yourself if you were to use RPC for bulk
data transport in your application, and it wouldn't plug into "read" and
"write" in most UNIX systems without some work.