[jira] Commented: (SLING-967) Support davmount requests (RFC 4709)
[ https://issues.apache.org/jira/browse/SLING-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708831#action_12708831 ] Julian Reschke commented on SLING-967: -- More implementation support: * Xythos Drive Windows client (== SAP Portal Drive) Question: how about doing this in a way so that it can also be easily used from the base Jackrabbit WebDAV servlet? Support davmount requests (RFC 4709) Key: SLING-967 URL: https://issues.apache.org/jira/browse/SLING-967 Project: Sling Issue Type: New Feature Components: JCR Affects Versions: JCR Webdav 2.0.4 Reporter: Felix Meschberger RFC 4709 [1] defines a file format and MIME type to convey WebDAV mount information from servers to clients. Generating such a response is easy for Sling in that the WebDAV support can register servlet responding to the davmount extension, which maps to the application/davmount+xml extension. This servlet would generate the correct response. For example a request to http://host/some/content.davmount might reply with dm:mount xmlns:dm=http://purl.org/NET/webdav/mount; dm:urlhttp://host:80//dm:url dm:opensome/content//dm:open /dm:mount [1] http://www.ietf.org/rfc/rfc4709.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: WebDav Node properties
Bertrand Delacretaz wrote: On Mon, Apr 20, 2009 at 5:45 PM, Carl Hall carl.h...@gmail.com wrote: Are node properties viewable/changeable through webdav access to a JCR repo? Not AFAIK, WebDAV is about files...I *think* there's an enhanced WebDAV component in Jackrabbit that allows for some additional JCR remoting, can anyone confirm? Hu? WebDAV is about properties as well, and I'm pretty sure the Jackrabbit WebDAV servlet supports this... BR, Julian
sling examples: sling-generated path
Hi, I was just looking at the sling-in-15min tutorial, and came across the section Let Sling generate the path of a newly created node, which describes using POST and * as last path segment... Out of curiosity: why not just POST to the location? That seems to be more in sync with how POST is defined in HTTP... BR, Julian
Re: sling examples: sling-generated path
David Nuescheler wrote: Out of curiosity: why not just POST to the location? That seems to be more in sync with how POST is defined in HTTP... for known resources this is the case... and everybody is welcome to do that. Sure; in *that* case of course PUT is right... in some cases, sling should be put in charge to create something new and unique without the developer having to choose... let's say adding new comments to a blog post for example. That's the case I was thinking of... anyway, in hind-sight the /xyz/* for the POST is probably not ideal and in my mind should be deprecated in favour of /xyz/ with a trailing slash. Yep. That would align it with how adding to collections works in AtomPub. BR, Julian
Re: sling examples: sling-generated path
Bertrand Delacretaz wrote: On Thu, Oct 16, 2008 at 5:14 PM, David Nuescheler [EMAIL PROTECTED] wrote: ...anyway, in hind-sight the /xyz/* for the POST is probably not ideal and in my mind should be deprecated in favour of /xyz/ with a trailing slash The problem with not using xyz/* is differentiating between create and modify operations. If a POST to xyz/ always creates a new node under it, how to you update a property on xyz itself? Being able to use PUT would be the answer, but browsers don't do that. Browsers do with XHR; is this required to work with forms? (as you can guess from that question, I'm a total newbie wrt Sling). We could have used HTTP headers to make a POST behave like a PUT, but I think the magic star is easier to use from browsers, and more visible than a HTTP header. It's definitively better than a header. So my answer is: we currently use xyz/* as a workaround, to differentiate between create and modify when working with today's browsers as clients. One could imagine other ways to hack it into the URL, such as path parameters or query parameters... BR, Julian
Re: sling examples: sling-generated path
Julian Reschke wrote: ... So my answer is: we currently use xyz/* as a workaround, to differentiate between create and modify when working with today's browsers as clients. One could imagine other ways to hack it into the URL, such as path parameters or query parameters... ... Speaking of which... http://greenbytes.de/tech/webdav/draft-reschke-webdav-post-latest.html makes a proposal for a way to discover that kind of POST-for-add-member-URL for WebDAV, but it might be applicable here as well (see in particular http://greenbytes.de/tech/webdav/draft-reschke-webdav-post-latest.html#rfc.section.3.2.3). BR, Julian
