OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (CMIS-700) Remove cmis:pageInfo(defined in section 1.2.4)



     [ http://tools.oasis-open.org/issues/browse/CMIS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Melahn updated CMIS-700:
--------------------------------

    Proposal: 
Remove this section from the proposal...

1.2.4 Paging

Since the number of objects returned from the navigation services can be huge, a mechanism for paging is provided.   The optional input parameters defined on the navigation services, maxItems and skipCount, shall be represented as request parameters of the same name.   

A JSON object with the key "cmis:pageInfo" shall be present if the request parameter maxItems is present or if the repository returns less than the total number of items in the repository.   This object shall have the following JSON key/value pairs.  

boolean hasMoreItems
number numItems

See the description in Section 2.2.1.1 for the meaning of these parameters.

Example:


GET /cmis/repository/123/myFolder?maxItems=10 HTTP/1.1
	Host: www.example.com
	User-Agent: Mozilla/5.0

HTTP/1.1 200 OK
   Content-Type: application/json
   Content-Length: xxxx

{cmis:pageInfo": 
  {
  "hasMoreItems": true,
  "numItems": 127
  }
}
 . . . 




> Remove cmis:pageInfo (defined in section 1.2.4)
> -----------------------------------------------
>
>                 Key: CMIS-700
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-700
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Browser Binding
>    Affects Versions: Browser Binding Proposal
>            Reporter: Florian Mueller
>            Assignee: Gregory Melahn
>             Fix For: Browser Binding Proposal
>
>
> Paging information is now inherent part of the appropriate types in the schema. There is no need for cmis:pageInfo anymore.

-- 
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]