[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CAMP-42) Spec should say how to limit/specify the scope of returned data
[ http://tools.oasis-open.org/issues/browse/CAMP-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Chapman updated CAMP-42:
--------------------------------
Proposal:
from scrum session 1:
close CAMP-42 with no action. there are many attempts at different levels (e.g. http) and to do correctly is too big a job for 1.1. Note that we have re-factored to minimize where the large arrays are are.
> Spec should say how to limit/specify the scope of returned data
> ---------------------------------------------------------------
>
> Key: CAMP-42
> URL: http://tools.oasis-open.org/issues/browse/CAMP-42
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Task
> Components: Spec
> Reporter: Alex Heneveld
> Assignee: Alex Heneveld
>
> Currently the spec only dictates requests whose response is an entire Resource object. These Resources could be very large however, and it is wasteful for everyone to send the entire object if, as will commonly be the case I expect, the client is only interested in a small piece of the Resource.
> This spec should define how a client can restrict a query to selected items of the Resource. This should include:
> * filtering: selecting a specific key or restricting to a set of keys
> * pagination: selecting a specific element or range of elements (where a key's value is of type list)
--
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]