From: Thomas Lord <lord@emf.net>
To: emacs-devel@gnu.org
Subject: webdav advice sought
Date: Tue, 23 Jun 2009 16:26:59 -0700 [thread overview]
Message-ID: <1245799619.5916.145.camel@dell-desktop.example.com> (raw)
I am working on a project that includes improving
"webdav support in Emacs". I plan to submit patches
and/or new code. I am writing to cross check my
thinking about how to do this before I get too
deeply into it.
I would appreciate helpful suggestions about
what information I'm missing, about which of my
alternative (tentative) plans makes the most sense,
and about what better plans I might have missed.
WebDAV is, of course, a protocol layered on top
of HTTP providing support for a remote file system.
I would like Emacs to be able to treat WebDAV servers
as a regular file system - to be able to "find-file"
a WebDAV file, to be able to save files, to have dired
work and so forth. I would like advisory locking to work.
I would like to, at least by default, have auto-save files
go locally. I am explicitly not, at this stage, concerned
with the WebDAV features and extensions related to versioning.
I understand that there is limited VC-mode support
for WebDAV though I don't know much about that yet.
That is not quite what I'm looking for (I think). I
understand similarly about w3 mode webdav support.
I understand that there is some (somewhat bit-rotted) support
from a third party package called "eldav", which relies on
an unmaintained program called "nd". The current state
of ange-ftp-like support for WebDAV is a bit sad, as far
as I can tell.
First question: have I missed something about the current
state of things?
Second question: what makes sense here?:
1. Try to rehabilitate eldav?
2. Try to adapt ange-ftp to use "cadaver", a command-line
webdav client similar to typical ftp client programs?
3. Try to adapt tramp, again using cadaver?
4. Use ange and tramp as a guide but write a new set
of file hooks, presumably using cadaver?
5. One of the above, but don't use cadaver, use ______?
6. Write C code for Emacs core (adding new library dependencies)?
7. Tom, you dummy, none of the above. Instead ________?
I have my preferences from the above list but I
won't bias things yet by stating them.
Thanks and Regards,
-t
next reply other threads:[~2009-06-23 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 23:26 Thomas Lord [this message]
2009-06-24 1:09 ` webdav advice sought David Reitter
2009-06-24 17:44 ` Thomas Lord
2009-06-24 1:56 ` Jason Rumney
2009-06-24 4:49 ` Michael Albinus
2009-06-24 5:07 ` Thomas Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245799619.5916.145.camel@dell-desktop.example.com \
--to=lord@emf.net \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).