Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!nrl-cmf!ukma!tut.cis.ohio-state.edu!bloom-beacon!apple!bionet!agate!ucbvax!TWG.COM!mrose
From: mrose@TWG.COM (Marshall Rose)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: RCP and LOTOS
Message-ID: <832.597725096@twg.com>
Date: 10 Dec 88 02:44:56 GMT
References: <1588*carlos@deervax.concordia.ca>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: tcp-ip@sri-nic.arpa
Organization: The Internet
Lines: 15

There are a number of fundamental differences in the OSI remote
operations model from the traditional RPC mechanism used, e.g., by Sun.
Although a number of these might be addressed over time (e.g., at the
moment all OSI remote operations are based on a connection-oriented
transport), it's not clear how much will carry over.

I recently re-cast rsh using OSI remote operations, calling the result
"osh".  Although the ROS-based protocol was fairly simple,
implementation of it was very painful in comparison to rsh.  A lot of
this is due to the amazing similarity between the service raw TCP gives
you (a reliable byte stream) and what a UNIX pipe offers.  In contrast,
OSI remote operations, while connection-oriented, still pass discrete
units (i.e., use of ASN.1, et. al., imposes structure).

/mtr