[OASIS Issue Tracker] Commented: (CMIS-42) getDescendants shouldhave maxItems/skipCount

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10111#action_10111 ] 

Julian Reschke commented on CMIS-42:
------------------------------------

Note that RFC 5005, Section 3 states:

"Paged feeds are lossy; that is, it is not possible to guarantee that clients will be able to reconstruct the contents of the logical feed at a particular time. Entries may be added or changed as the pages of the feed are accessed, without the client becoming aware of them." -- <http://greenbytes.de/tech/webdav/rfc5005.html#rfc.section.3.p.2>

So maybe CMIS needs to add requirements here (which?), or use a different mechanism.

> getDescendants should have maxItems/skipCount
> ---------------------------------------------
>
>                 Key: CMIS-42
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-42
>             Project: OASIS Content Management Interoperability Services TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.50
>            Reporter: Florent Guillaume
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> getDescendants may return even more information than getChildren, so the maxItems/skipCount batching controls that getChildren has are even more important for getDescendants.

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