Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!ncar!groucho!davis
From: davis@groucho.ucar.edu (Glenn P. Davis)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Are sockets the wave of the future?
Message-ID: <8371@ncar.ucar.edu>
Date: 30 Aug 90 23:57:56 GMT
References: <9008281330.AA00189@atlantic.nprdc.navy.mil>
Sender: news@ncar.ucar.edu
Organization: University Corporation for Atmospheric Research (UCAR)
Lines: 24

In <9008281330.AA00189@atlantic.nprdc.navy.mil> stanonik@NPRDC.NAVY.MIL (Ron Stanonik) writes:

>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

Sun RPC includes a provision for 'batched' rpc's. The procedure call
doesn't wait for a return.
We have an set of applications based on Sun RPC which use this to "blast 
variable and voluble amounts of data at a server.

Glenn P. Davis
UCAR / Unidata
PO Box 3000                   1685 38th St.
Boulder, CO 80307-3000        Boulder, CO  80301

(303) 497 8643