[OASIS Issue Tracker] (ODATA-1261) Allow $pagesize system query option

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

Evan Ireland created ODATA-1261:
-----------------------------------

             Summary: Allow $pagesize system query option
                 Key: ODATA-1261
                 URL: https://issues.oasis-open.org/browse/ODATA-1261
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: URL Conventions
    Affects Versions: V4.01_CS02
            Reporter: Evan Ireland


Using an HTTP header for client's preferred pagesize is problematic, particularly when the client-specified query URL uses $expand.

While a server is free to ignore any client-specified pagesize, it is beneficial to be able to have the client indicate their preference for each "node" in a URL using that has one or more $expands, so that the server (if it is agreeable) may respect the client's intentions.

Also we may consider whether such a system query option could be used by the client to indicate that they want a "deferred" expansion of a navigation property, e.g.

  Customers?$expand=Orders($pagesize=-20)

page size of 20, but return initially an empty collection and a next-link (for page size 20).

whereas:

  Customers?$expand=Orders($pagesize=20)

Âwould be expected to return initially a collection of 20 items, then a next link for page size 20.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)