[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CMIS-188) Should it be optional tosupport "getDescendants" with an arbitrary "depth"?
[ http://tools.oasis-open.org/issues/browse/CMIS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Gur-esh updated CMIS-188: ------------------------------- Component/s: Domain Model > Should it be optional to support "getDescendants" with an arbitrary "depth"? > ---------------------------------------------------------------------------- > > Key: CMIS-188 > URL: http://tools.oasis-open.org/issues/browse/CMIS-188 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Components: Domain Model > Reporter: Ethan Gur-esh > Assignee: Ethan Gur-esh > Priority: Minor > Fix For: Draft 0.62 > > > The current definition of the "getDescendants" method can take in 3 values for the "depth" parameter: > * 1: Which behaves like GetChildren > * -1: Which gets ALL descendants, regardless of depth > * [2..n]: Which gets ONLY decendants up to the depth level specified. > But I'm not sure that many repositories can handle the [2..n] case very efficiently. (E.g. in SharePoint the native data tables make this query non-trivial to execute, even though the "-1" and "1" cases are very efficient.) > Should we provide a way for repositories to say that they don't support getting an arbitrary depth of children? Or maybe just remove that case, by saying that getChilren is ALWAYS with a depth of "-1" (i.e. remove the parameter entirely?) -- 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]