Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!NPRDC.NAVY.MIL!stanonik
From: stanonik@NPRDC.NAVY.MIL (Ron Stanonik)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Are sockets the wave of the future?
Message-ID: <9008281330.AA00189@atlantic.nprdc.navy.mil>
Date: 28 Aug 90 13:30:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: stanonik@nprdc.navy.mil
Organization: The Internet
Lines: 17

> Dear Dan,
> 	You seem to understand these things, so maybe you can help me
> with a little semantic problem. Every time I feed a .x file to rpcgen,
> it insists on spitting out client and server stubs, which I find
> convenient for building my distributed applications.  Yet you say that
> RPC wasn't designed for client-server applications.  I'm confused...

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).
The non-network implementation of such usually consists of write/puts/printf
to stdout, but RPC doesn't seem to contain a stream type, such that you keep
reading from it until EOF.

Ron Stanonik
stanonik@nprdc.navy.mil