[OASIS Issue Tracker] (ODATA-1048) Move server-driven paging to advanced conformance level

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

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

Michael Pizzo commented on ODATA-1048:
--------------------------------------

The key here is:  MUST support server-driven paging *when returning partial results* (section 11.2.5.7)

That is, the service is not allowed to use other alternate paging mechanisms (such as the client needing to know to ask for additional pages).  It is *NEVER* required that a service return partial results at any conformance level, but it IS required that IF any odata-compliant service returns a partial result, then it MUST include a next link as per section 11.2.5.7.

Agree that we can clarify the text.



> Move server-driven paging to advanced conformance level
> -------------------------------------------------------
>
>                 Key: ODATA-1048
>                 URL: https://issues.oasis-open.org/browse/ODATA-1048
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Protocol
>    Affects Versions: V4.01_CSD01
>         Environment: Proposed
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: V4.01_CSD02
>
>
> Why is server-driven paging a MUST for minimal conformance? It's more of a self-defense mechanism and not needed for services with modest amounts of data.



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