You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/05/13 08:46:45 UTC
[jira] Created: (SLING-967) Support davmount requests (RFC 4709)
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:url>http://host:80/</dm:url>
<dm:open>some/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.
[jira] Commented: (SLING-967) Support davmount requests (RFC 4709)
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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:url>http://host:80/</dm:url>
> <dm:open>some/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.
[jira] Commented: (SLING-967) Support davmount requests (RFC 4709)
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708809#action_12708809 ]
Felix Meschberger commented on SLING-967:
-----------------------------------------
Implementation support:
* For Windows, the RFC contains the source for a Windows Script allowing to open davmount responses with Windows WebFolder
* For Linux a gvfs-dav-mount tool is available in source from from http://github.com/gicmo/gvfs-dav-mount/tree/master
> 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:url>http://host:80/</dm:url>
> <dm:open>some/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.
[jira] Commented: (SLING-967) Support davmount requests (RFC 4709)
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708840#action_12708840 ]
Felix Meschberger commented on SLING-967:
-----------------------------------------
For the base Jackrabbit WebDAV servlet, I would have proposed an IOHandler. But this has two drawbacks: (1) it would collide with the DirListingHandler and (2) trying to use a special extension will not easily work.
Another option would be to overwrite the AbstractWebDavServlet.doGet method and check for the .davmount extension if the resource does not exist and return the dav mount response in this case....
Anyway, apart from the very simple core response generation, there is probably nothing, which could be shared...
> 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:url>http://host:80/</dm:url>
> <dm:open>some/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.