I like the webDAV approach because one can use it with so many different
editors. Most desktop web editors support webDAV and have for a while.
If the editor doesn't support webDAV, well, just make a web folder
(windows) or mount_webdav (mac, which doesn't work yet, think it doesn't
like the way the depth header isn't respected currently).
The ability to build up a publication in Lenya from an existing site
using drag and drop is really nice :).
--Doug
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
I think that's actually a plus ;-), because it hopefully
means you tend to a more generic approach.
considering that CMS are written in all kinds of languages and running
on all kinds of platforms, a protocol-based approach seems the only
sensible choice. we already use PUT in many editors, and kupu models the
WebDAV model of resources and collections.
http://codespeak.net/svn/kupu/trunk/kupu/doc/LIBRARIES.txt has more on
this. lenya 1.4 now has webdav support. ideally, custom config details
could be determined via PROPGET.
as far as i understand, both kupu and bxe already ship with a js webdav
library. ironically, it seems to have originated in an earlier oscom
effort: http://twingle.mozdev.org/
how is OSR-1 different from twingle? it seems to me it would make more
sense to finish what we started with twingle long ago rather than embark
on a new mission to rediscover the same solutions :)
twingle has since been partly incorporated into kupu (and parts into bxe
as well), from what i understand
the other protocol, the ATOM api, would also be nice, but would not play
nicely with desktop applications (where webdav is really the story)
WDYT?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
