[OASIS Issue Tracker] (ODATA-942) How should headers applied to a batch affect statements within a batch?

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

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

Michael Pizzo updated ODATA-942:
--------------------------------

    Proposal: We probably need to spell out semantics for each header when applied to a batch.  (was: Either state that headers on the batch are ignored or spell out semantics for each header when applied to a batch.)

> How should headers applied to a batch affect statements within a batch?
> -----------------------------------------------------------------------
>
>                 Key: ODATA-942
>                 URL: https://issues.oasis-open.org/browse/ODATA-942
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> Today we don't spell out how setting a header on a batch affects individual statements of the batch, nor do we specify what happens if the same header is specified on the batch and the individual statement with different values.
> Do we ignore headers on the batch? Do we define a precedence rule where headers on the batch define defaults, but headers on the individual statements take precedence.  For something like include-annotations, does a precedence rule imply that, if an annotation is included in the batch and not specified in the individual request, it is included, if an annotation is excluded in the batch and not specified in the individual request it is excluded, if an annotation is included in the batch and excluded in the individual request it is excluded, and if an annotation is excluded in the batch but included in the request it is included?



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