From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8eeddd807352533475a45f64e8f8c293@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] WebDAV file system
From: "Skip Tavakkolian" <fst@centurytel.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 29 Oct 2002 23:10:13 -0500
Topicbox-Message-UUID: 11b66130-eacb-11e9-9e20-41e7f4b1d025

WebDAV tries to provide a filesystem abstraction with a URI based
namespace and uses HTTP for transport. The description of the data (file
attributes and payload) is in XML. Atomic unit of data is a file (PUT, GET, etc.)
In a superficial way it is like 9P, but not in details or what it's going after.

If you just want the client side (mentioned in another email), then as
Russ suggests, you should have a short way to go from webfs.  You'd
have to figure out the mapping between PUT/GET/POST/MKCOL/LOCK/etc
and 9P calls.

> There seems to be a fair bit of overlap in the goals and functionality of
> WebDAV and 9P so I was wondering how feasible it would be (I'm a reasonably
> competent C programmer) to attempt writing a WebDAV file system for Plan 9
> (i.e., essentially a WebDAV equivalent to ftpfs).  I thought it would be an
> interesting project to teach me Plan 9 programming.
>
> I'm assuming that given HTTP is a stateless protocol that it would be
> simpler than ftpfs.  Could much be re-used from webfs?