[OASIS Issue Tracker] (ODATA-745) Sections 4.5.4 and 4.5.5: odata.count and odata.nextLink are allowed for all collections

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

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

Evan Ireland edited comment on ODATA-745 at 11/11/14 10:42 PM:
---------------------------------------------------------------

Allowing non-navigation collections to have nextLink can be highly inconvenient for clients, which may end up having to implement parsing of "values" interspersed with fetching of network resources, i.e. it does not allow for a clean separation of network access and response parsing.

Perhaps any relaxation to allow nextLink for non-entity collections should be enabled via the HTTP Prefer header?



was (Author: evan.ireland):
Allowing non-navigation collections to have nextLink can be highly inconvenient for clients, which may end up having to implement parsing of "values" interspersed with fetching of network resources, i.e. is does not allow for a clean separation of network access and response parsing.

Perhaps any relaxation to allow nextLink for non-entity collections should be enabled via the HTTP Prefer header?


> Sections 4.5.4 and 4.5.5: odata.count and odata.nextLink are allowed for all collections
> ----------------------------------------------------------------------------------------
>
>                 Key: ODATA-745
>                 URL: https://issues.oasis-open.org/browse/ODATA-745
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_ERRATA03
>
>




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