Path: utzoo!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!intercon!news
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.protocols.nfs
Subject: Re: NeFS protocol
Message-ID: <266293A9.70C9@intercon.com>
Date: 29 May 90 15:22:17 GMT
Article-I.D.: intercon.266293A9.70C9
References: <1990May24.034258.13625@Neon.Stanford.EDU> <3378@auspex.auspex.com> <1990May24.205149.6065@Neon.Stanford.EDU> <3385@auspex.auspex.com> <1990May25.234950.1465@Neon.Stanford.EDU> <265DFAD2.5818@intercon.com> <1990May26.213221.15248@Neon.Stanford.EDU>
Sender: usenet@intercon.com (USENET The Magnificent)
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Organization: InterCon Systems Corporation, Herndon, VA
Lines: 13

In article <1990May26.213221.15248@Neon.Stanford.EDU>, pallas@Neon.Stanford.EDU
(Joe Pallas) writes:
> And filesystem code will be even more complicated than graphics code,
> which is hard enough for humans to read and write in PostScript.

Depends on the human, I guess :-).  I don't see how writing file system
client code in C (even with RPCGEN) is any easier, though...

--
Amanda Walker, InterCon Systems Corporation
--
"Go not to the elves for counsel, for they will say both no and yes."
	--J.R.R. Tolkien, The Lord of the Rings