Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!emory!gatech!mcnc!rti!bnrunix!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: gene@ponder.csci.unt.edu (Gene De Lisa)
Newsgroups: comp.sys.sun
Subject: Use of RPC
Keywords: Miscellaneous
Message-ID: <2031@brchh104.bnr.ca>
Date: 21 Mar 91 21:31:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 23
Approved: Sun-Spots@rice.edu
X-Original-Date: Fri, 15 Mar 91 16:12:08 GMT
X-Sun-Spots-Digest: Volume 10, Issue 58, message 24
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

My development group is now in the process of designing a future hardware
and software platform for our product.  We require both an internal
technique for our various processes to communicate with each other, and
also a well-defined interface by which new processes can be written (by
somebody else) to exchange data with our programs.

It seems to me that the RPC mechanism is well suited to both tasks.
However, I don't want to start using something that is non-standard or
will be phased out within a few years.  (This is why we don't want to use
sockets.)

Given a SPARC platform, it seems that the choice is between using TLI or
using RPC.  Is RPC generally viewed as an excentric Sun specific oddity,
or is it the wave of the future?  I hope this question does not have
religious overtones . . .

Any insights, advice, or telling of the future would be appreciated.
Please send mail to tim@grenada.bellcore.com (not to tim@grenada.uucp,
that goes to Island Graphics and they probably know this stuff already).
Thanks!

Tim J Ihde				tim@grenada.bellcore.com
(908) 699-2487