From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] vfork and paging From: David Gordon Hogan MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20011019210446.3115019A02@mail.cse.psu.edu> Date: Fri, 19 Oct 2001 17:03:07 -0400 Topicbox-Message-UUID: 0b2341f4-eaca-11e9-9e20-41e7f4b1d025 > You're not dreaming, but webfs is not what you might call functional > yet. It's unclear whether it'll ever be. I don't know who uses it here. %g ls -ld /sys/src/cmd/webfs d-rwxrwxr-x M 8 dhog sys 0 Oct 1 09:44 /sys/src/cmd/webfs Thanks for the vote of confidence :-) A summer intern here wrote a file system called "urlfs". Basically a "clone" style interface for fetching web pages, which decouples the transport from the browser. I've been cleaning it up in an idle thread. I renamed it webfs, made it work with the new 9p library, and started to add plumbing support before I got thoroughly disgusted with the code. A rewrite is required. In the future, URLs will be plumbed to webfs. Webfs will start fetching the URL, determine the Mime type, and send a new plumb message with a path name under /mnt/web as the data, and the Mime type as an attribute. The plumbing rules will then determine the correct destination (eg Charon, page, acme, ...) from the Mime type (with file suffix as fallback). This will be a vast improvement over the existing model, which erroneously assumes that all http:// urls should be handled by an html browser... Frame subsidiaries with be handled by Charon (or i) through the existing clone interface.