jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (JCR-3005) Make it possible to get multiple nodes in one call via davex
Date Thu, 06 Oct 2011 10:58:29 GMT

    [ https://issues.apache.org/jira/browse/JCR-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121832#comment-13121832
] 

Jukka Zitting edited comment on JCR-3005 at 10/6/11 10:56 AM:
--------------------------------------------------------------

As a general rule I wouldn't consider us committed to providing backwards compatibility on
any feature that we haven't documented (I'd count a relevant Jira issue marked as resolved
in a specific release as the minimal level of documentation about a new feature). Anyway,
I see your point and will make sure that this is either resolved in time for 2.3.1 or that
the feature is disabled in the release until we have consensus about the exact implementation.

In revision 1179564 I changed this feature to respond only to GET requests on a workspace
resource. If such a request contains one or more :path parameters, then the JSON response
containing information about all the identified nodes/subtrees is returned. For example:

    $ curl http://localhost:8080/server/default?:path=/node1&:path=/node2
    {"nodes":{"/node1":{...},"/node2":{...}}}

An optional :depth parameter can be used to override the configured default subtree depth
to include. Note that the current code doesn't support the configuration of default depth
per node type, only the overall default depth is used.

Notes:

* I prefer GET over REPORT for this since GET requests are generally easier to handle by many
clients and they are better understood by various intermediaries like web proxies or firewalls

* I see the point of using POST instead of GET for a large request, but I'd rather handle
that using a generic POST-to-GET conversion so we can support both GET and POST requests for
this information.
                
      was (Author: jukkaz):
    As a general rule I wouldn't consider us committed to providing backwards compatibility
on any feature that we haven't documented (I'd count a relevant Jira issue marked as resolved
in a specific release as the minimal level of documentation about a new feature). Anyway,
I see your point and will make sure that this is either resolved in time for 2.3.1 or that
the feature is disabled in the release until we have consensus about the exact implementation.

In revision 1179564 I changed this feature to respond only to GET requests on a workspace
resource. If such a request contains one or more :path parameters, then the JSON response
containing information about all the identified nodes/subtrees is returned. For example:

    $ curl 'http://localhost:8080/server/default?:path=/node1&:path=/node2'
    {"nodes":{"/node1":{...},"/node2":{...}}}

An optional :depth parameter can be used to override the configured default subtree depth
to include. Note that the current code doesn't support the configuration of default depth
per node type, only the overall default depth is used.

Notes:

* I prefer GET over REPORT for this since GET requests are generally easier to handle by many
clients and they are better understood by various intermediaries like web proxies or firewalls

* I see the point of using POST instead of GET for a large request, but I'd rather handle
that using a generic POST-to-GET conversion so we can support both GET and POST requests for
this information.
                  
> Make it possible to get multiple nodes in one call via davex
> ------------------------------------------------------------
>
>                 Key: JCR-3005
>                 URL: https://issues.apache.org/jira/browse/JCR-3005
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-server
>            Reporter: Christian Stocker
>            Assignee: Jukka Zitting
>             Fix For: 2.3.1
>
>         Attachments: getSessions.patch
>
>
> I'm working on this currently

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message