[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (CAMP-186) Pagination
[ https://issues.oasis-open.org/browse/CAMP-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilbert Pilz updated CAMP-186: ------------------------------ Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/58778/camp-spec-v1.2-wd11-issue-186-v2.doc (was: Concrete proposal outline: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/58646/camp-spec-v1.2-wd11-issue-186-v1.doc) > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]