• Hide

      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 }

      }
      . . .

      Show
      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 } } . . .
    • Hide

      section removed

      Show
      section removed

      Paging information is now inherent part of the appropriate types in the schema. There is no need for cmis:pageInfo anymore.

            Assignee:
            Gregory Melahn (Inactive)
            Reporter:
            Florian Müller (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: