From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200006300133.VAA28726@cse.psu.edu> From: "James A. Robinson" To: 9fans@cse.psu.edu Subject: Re: [9fans] gtk port In-reply-to: Message from Randolph Fritz of "Thu, 29 Jun 2000 15:51:59 PDT."References: <20000629155159.A7064@cyber-dyne.com> <20000629211635.261.qmail@nx.aichi-u.ac.jp> <200006292202.SAA24290@cse.psu.edu> <20000629155159.A7064@cyber-dyne.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24768.962328835.1@aubrey.stanford.edu> Date: Thu, 29 Jun 2000 18:33:55 -0700 Topicbox-Message-UUID: cf46785a-eac8-11e9-9e20-41e7f4b1d025 > On Thu, Jun 29, 2000 at 10:27:08PM +0000, James A. Robinson wrote: > > I like the idea, but I think there would have to be more than one web > server name. If Plan 9 gets longer filenames, it would be Really > Neat to be able to say 'cat /http/www.sciencemag.org'... I was thinking of acme's model where each window get's it's own id and file system. So each host would have it's own hierarchy. My example was poor, I should have posted something along the lines of: /mnt/web/new/ctl (open a new proto://host:port) /mnt/web/new/get (get back an with data filled from GET) /mnt/web/id/get (quick 'n' dirty GET request) /mnt/web/id/set (set ?default? outgoing headers/httpauth) /mnt/web/id/post (longer data submissions?) /mnt/web/id/headers/* (incoming header response) /mnt/web/id/body (read the body of the response) Or somesuch. With a private namespace for each host, you don't worry about long filenames. Jim