Hi Fabiano, I think the problem with your proposal is that you don't really say what the WebDAV API is, what functions it will have. It is possible that what you have in mind will satisfy Gerhard's concerns (his thoughts on how we might use this were exactly what mine were). Please describe the actual interface (method signatures) in more detail. cheers, Robert PS. Please post to PlanetSoC.com as well. Gerhard Killesreiter wrote:
On Sun, 3 Jul 2005, Fabiano Sant'Ana wrote:
I'm Fabiano Sant'Ana, working in a WebDAV Interface for Drupal in SoC, may be you already know me from #Drupal@freenode.net (my nick is wundo). You can read my proposal here: http://wundo.net/soc/ Please comment and suggest changes.
I have to admit that my knowledge of webdav is rather limited. To me it is mainly http on steroids.
In your proposal you describe that you want to use webdav as a backup-tool for Drupal for both the files and the database.
While I am quite sure that this would work for the files (if they are in a webdav enabled directory), I am surprised that it would work for the database. I don't think that webdav has a way to access the database. Please let me know if I am wrong.
I see the same problem for usage of webDAV as a remote content creation tool. We already have various blogging methods for this.
The main use I see for webdav is for massuploading verious forms of non-text data that will be imported into Drupal through the execution of the cron hook.
It is probably also usefull to allow module upload through webdav and the node_import module. This module accept a csv file as input and currently relies on http post upload. I can imagine that webDAV could be used to upload larger csv files more efficiently. Adding node export in a similar way would allow for easier sharing of content.
Just a couple of thoughts.
Cheers, Gerhard