[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-42) getDescendants shouldhave maxItems/skipCount
[ http://tools.oasis-open.org/issues/browse/CMIS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10113#action_10113 ]
Florent Guillaume commented on CMIS-42:
---------------------------------------
Lossiness is already accounted for in the domain model, for instance getChildren has the note:
Between invocations the order of the results may change due to repository state changing, i.e. skipCount might not show objects or more likely show an object twice (bottom of first page and top of second) when an object is added to the top of the list.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]