🚀 go-pugleaf

Submitted-by: gwyn@smoke.brl.mil (Doug Gwyn)

In article <1js17fINNenp@ftp.UU.NET> davecb@nexus.yorku.ca (David Collier-Brown) writes:
>  I'd like to follow the implied RFC model a bit closer and define a
>protocol.  You know, like ``first you open the file, then read or write
>for a while, then close''.

Well, gee, once you look at it that way, the spooler interface ought to
be something like:
	cp print_me /dev/spool
where the /dev/spool filesystem takes care of assigning unique queue names,
etc. and for example
	ls /dev/spool/status | grep "^$MY_UID"
would show how your jobs are doing.
Of course that's a bit simplistic, but why should we even THINK about
introducing a new, different protocol for some set of open/read/write/close
actions when we already have a general one?  (Or should have.)


Volume-Number: Volume 30, Number 39