[OASIS Issue Tracker] Commented: (ODATA-317) Allow multiple reads in the same transaction

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32869#action_32869 ] 

Matthew Borges commented on ODATA-317:
--------------------------------------

In such a case there is nothing stopping the server implementer from not using server driven paging.  Also, I think a few weeks ago someone else on the committee suggested allowing the client to make a suggestion to the server about server driven paging (I can't remember the exact details or whether or not this was accepted or rejected).  Reads in a transactions would be another application of this; when the client knows for sure they are willing to get all the data, they just tell the server not to use server driven paging.

> Allow multiple reads in the same transaction
> --------------------------------------------
>
>                 Key: ODATA-317
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-317
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Batch Processing Format 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Matthew Borges
>            Priority: Minor
>             Fix For: V4.0_WD01
>
>
> Allow change sets of only read operations.  The idea being you can get a snap shot of potentially unrelated entities at an instance in time.  It would also be useful for deltas where you want to get all the changes (even for unrelated entities) within a single change set request at a certain point of time.

-- 
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