Re: [bug-myserver] WebDAV

[ivailo ilionov]

> Differently than the GUI task, WebDAV is more straight as the design
> phase is minimal and you can expect to start coding already after a
> week.  Many of the additional HTTP commands offered by WebDav can be
> completed in a day or even less (look for example at COPY or MOVE).

> http://www.myserverproject.net/reports/doxygen/html/
>
> I think, in case you'll work on WebDAV, that versioning should be left
> at the end if there is time for it as additional feature, at least
> related to GSOC but this doesn't mean you can't implement it after

I have a few questions which will help me to write the application.

I understand what webdav can provide ( i've read the rfc : ) ). I've
also read that
there are work arounds in the face of wiki's for example which also
deal with documents, authoring, versioning etc..
I've also looked at a package ( project) davfs2. So, what do the
project developers
expect of the webdav support in the server to be used for ?  To be
mounted as local
FS, or to easy development of web applications which require that
functionality ?

I'll assume that locking on write is desired, so probably shared
locking will be used on resources ?

I'm not sure how the files should be described ( stored ). I know that
( well, i've never heard actually ) for example the ext3 filesystem
doesn't support custom attributes.
Is there a native file system, which can help with this problem, or
should I describe
every file in an xml ? That is, instead of directly accessing the
file, on valid request,
the xml file which has the information about the resource and it's
attributes, and flags.. will be read?

I'll write if there are more questions : )