Torsten Schlabach wrote:
I am not sure if it will be a good idea to introduce more and more tricks
and exceptions to the Lenya URI space, such as
/dav/xyz
for WebDAV access to
/xyz
I think the problem is that we have one entry point that we talk to (the
top level sitemap) and we try to get very different things out of it, such
as
- fully rendered live view
- authoring view (WYSWYG)
- editable version of a document (for Kupu and BXE)
- WebDAV version
- ...
I'd feel much better if we had two doors into Lenya: One for rendering
(site visitor facing) and one for editing purposes (internally, site
builder team facing). This would especially offer a very clean way to shut
the "editing" door in live environments.
WDYT?
Sounds like a good idea. What should the door be?
Currently, that "door" is in the path, right?
ex: /default/authoring/features.html or /default/live/features.html
Are you talking about doors as separate instances of lenya?:
http://localhost:9999/default/features.html (authoring)
http://localhost:8989/default/features.html (webDAV)
http://localhost:9898/default/features.html (OSR-101)
http://localhost:8888/default/features.html (live) or
http://webserver:8888/default/features.html (live on another box sharing
repo)
perhaps I am way off base ;)
Regards,
Torsten
Renaud Richardet wrote:
Torsten Schlabach wrote:
I've been experimenting with Cadaver and Vim, and it worked OK.
With 1.4alpha1 or with a recent SVN version?
With a recent SVN. The basic editing with VIM worked very well.
BTW: has anybody tried OpenOffice as a WebDav client? I can open the url
http://localhost:8888/default/ but get the login page. I found no way to
pass the username and pwd so far.
I have tried OpenOffice and have the same problem. Open Office doesn't
pass a user-agent header
(http://www.openoffice.org/issues/show_bug.cgi?id=21599).
The webDAV usecases in 1.4 use the method in place of a lenya.usecase
parameter. This works great for all but the GET method which is also
used in the authoring area by a web browser. This is one of the reasons
for matching the user-agent header. The other reason is to
authenticate via basic auth instead of the web form that lenya provides.
These problems could be resolved by using the path to differentiate a
webDAV client ( GET /dav/default/authoring/index.html ). Changing the
path would cause problems with the page-envelope module (and usecases
that use it?).
I will double check, but in testing a few webDAV clients, it didn't
appear that they like redirects, sessions, or GET parameters.
--Doug
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
