[OASIS Issue Tracker] (CAMP-186) Pagination

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

    [ https://issues.oasis-open.org/browse/CAMP-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62977#comment-62977 ] 

David Laurance commented on CAMP-186:
-------------------------------------

There are two families of filtering use cases.  Exemplars below:

> Usability:  A management user wants to show only Assemblies that originate from a given Plan.

The filtering attribute ("plan") is available from the Assembly resource, and therefore filtering is a matter of pattern matching against that attribute.  Note that the Assembly refers to the PLan by URI, which can be relatively opaque.  A management user may prefer to filter on the Plan name rather than the URI, but even filtering on the URI will meet the simplest requirement for filtering.

> Authorization:  A management user is allowed to see a subset of Assemblies; the CAMP Provider must not deliver information about Assemblies for which the management user does not have appropriate access permission.

Authorization requirements are complex by nature and cannot be resolved in a general way within the current CAMP specification.  Existing implementations of the CAMP specification (e.g., Pantheon) have implemented partial solutions for this family of use cases, restricting visibility based upon user role and permissions.   End user identity is communicated between CAMP Consumer and CAMP Provider. The permission decision and filtering of results are implemented within the CAMP Provider.  Results are returned to the CAMP Consumer based upon the identified user's permission.

 

> Pagination
> ----------
>
>                 Key: CAMP-186
>                 URL: https://issues.oasis-open.org/browse/CAMP-186
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Priority: Minor
>
> A client consuming the List resources (such as assemblies) may need to consume a very large set of results and would generally expect to be able to issue a request for a sequence of sub-ranges either through http headers such as range & content-range, or through explicit parameters such as ?range=25&offset=24.  We should specify how this is to be done.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)