jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-416) Webdav Simple: Delegate PROPPATCH to (extended) IOHandlers
Date Tue, 15 Aug 2006 08:22:14 GMT
     [ http://issues.apache.org/jira/browse/JCR-416?page=all ]

angela updated JCR-416:
-----------------------

    Attachment: Litmus_rev_431546.txt

attached litmus results

> Webdav Simple: Delegate PROPPATCH to (extended) IOHandlers
> ----------------------------------------------------------
>
>                 Key: JCR-416
>                 URL: http://issues.apache.org/jira/browse/JCR-416
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: webdav
>    Affects Versions: 1.0
>            Reporter: angela
>         Assigned To: angela
>         Attachments: Litmus_rev_431546.txt
>
>
> complete description:
> http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/6582
> Proposed solution
> ------------------------------------------------------------------------------------------------------------------------------------
> The situation described before leads me to the following conclusion:
> - IOHandler should not only read/write resource data and properties during GET, PUT,
PROPFIND but should
>    also take care of setting/removing properties upon PROPPATCH.
> - Since the previous suggestion would still limit the properties to (jcr:encoding, jcr:mimeType
and
>    jcr:lastModified), we may think about changing the default nodetype for the jcr:content
node to
>    nt:unstructured.
> I guess this would meet the requirements for those expecting a webDAV server that is
(as a first step)
> not limited regarding PROPPATCH. Second it would allow to have a handling of property
modifications
> which is specific for individual resource types instead of trying to set all properties
to the uppermost node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message