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


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

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

Subject: [OASIS Issue Tracker] Updated: (ODATA-519) Define server-driven paging for collection-valued resources

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

Ralf Handl updated ODATA-519:

    Environment: [Applied]  (was: [Applying])

> Define server-driven paging for collection-valued resources
> -----------------------------------------------------------
>                 Key: ODATA-519
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-519
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD03
> We allow client-driven paging with $top and $skip for all collection-valued resources, but restrict server-driven paging (indicated by next links) to collections of entities or entity references.
> Semantically there's no reason for this restriction, and both Atom and JSON would naturally allow this with <link rel="next" ../> or odata.nextLink in the collection wrapper.
> The obvious work-around of returning a collection of transient entities with a dummy key is sub-optimal.

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]