Michael Wechner wrote:
Doug Chestnut wrote:
Yeah, I started with that approach, but ran into problems with things
like the page-envelope and usecases not recognizing the path.
right, but why did you actually need the page-envelope resp what usecases?
Don't have time to look for examples now ;).
Using the same path made it allot easier to make the usecases as I
didn't have to rewrite methods that expect the standard path format (
DocumentUsecase.getSourceDocument ). I was even able to simply use the
existing delete usecase for the DELETE method.
How about the authorizer action? Doesn't this expect the general path?
--Doug
Thanks
Michi
Haven't tried it, but it looks like zope uses another port for webDAV.
Playing around yesterday, it was easy to add a jetty listener on
another port. Changing a couple of sitemaps and I have a webDAV
specific port. The webDAV clients that I have tested so far work, but
OO seems to have problems. I will take a closer look today.
--Doug
Michael Wechner wrote:
Doug Chestnut wrote:
Yeah, I am not sure that I like the idea of running another instance
of lenya just for webDAV, don't know if cocoon/jetty can run on
multiple ports without starting up another jetty instance.
what about a reserved prefix, e.g.
http://foo.bar/lenya/MY-PUB/webdav/....
IIRC that's what I did with the blog publication ...
HTH
Michi
Thanks,
Manos
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
