Re: Random idea:
- To: "George A. Dowding" <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: Random idea:
- From: Tomasz Wegrzanowski <firstname.lastname@example.org>
- Date: Sun, 2 Jan 2000 01:33:16 +0100
- Message-id: <[🔎] 20000102013316.A2078@priv3.onet.pl>
- In-reply-to: <email@example.com>; from firstname.lastname@example.org on Thu, Dec 30, 1999 at 01:10:51PM -0900
- References: <email@example.com> <Pine.LNX.firstname.lastname@example.org> <email@example.com>
On Thu, Dec 30, 1999 at 01:10:51PM -0900, George A. Dowding wrote:
> * Obligatory Random Idea:
> Has anyone taken a look at Plan 9/Inferno. They have made some
> interesting design decisions. One of the most interesting is to
> elevate the concept of files. Not only are all physical devices files
> (like Unix), but running programs can be treated as files. An example
> given was a name server. To get the information a process would write
> the request to the name server file. Reading that same file after the
> request would provide the address information. Apperently the idea
> was to limit the type of operations that processes had to provide to
> basic file reads and writes.
> To make a shell metaphor:
> $echo gnu.hurd.org > /system/nameserver
> $cat /system/nameserver
> Name: www.gnu.org
> Address: 126.96.36.199
> Aliases: hurd.gnu.org
Does it have to be opened between writing a request and reading a response ?
If it have to, it makes using such files from shell quite difficult.
Either designing system where file doesnt have to be opened (how requests and responses
are to be linked then, we cannot rely on the same order of reads and writes) or
designing shell which can keep files opened between read and write is a bit problematic.