Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!usc!apple!agate!shelby!neon!pallas
From: pallas@Neon.Stanford.EDU (Joe Pallas)
Newsgroups: comp.protocols.nfs
Subject: Re: NeFS protocol
Message-ID: <1990May25.234950.1465@Neon.Stanford.EDU>
Date: 25 May 90 23:49:50 GMT
References: <1990May24.034258.13625@Neon.Stanford.EDU> <3378@auspex.auspex.com> <1990May24.205149.6065@Neon.Stanford.EDU> <3385@auspex.auspex.com>
Organization: Computer Science Department, Stanford University
Lines: 20

In article <3385@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris)
writes:

>...people don't generally write NeFS programs, NeFS client code writes
>NeFS programs.

I've never written any NeFS client code, so maybe I'm talking through
my hat, but I doubt that NeFS client code is likely to write NeFS
programs.  NeFS client code is likely to ship NeFS programs over to
the server once (at initialization), and then invoke those programs
with the appropriate arguments as desired.  Now you may call those
invocations programs, but they're really just RPCs.  The server-side
programs being invoked by those RPCs will almost certainly by written
by humans.

Anyone with experience writing NeFS (or NeWS) clients is welcome to
contradict me.  (Use of PostScript as a compiler target language does
not count.)

joe