[OASIS Issue Tracker] (ODATA-541) Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

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

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

Ralf Handl updated ODATA-541:
-----------------------------

    Labels: AdoptionBlocker  (was: )

> Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-541
>                 URL: https://issues.oasis-open.org/browse/ODATA-541
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Implementing OData, OData Batch Processing Format
>    Affects Versions: V4.0_CS01
>            Reporter: Matthew Borges
>              Labels: AdoptionBlocker
>             Fix For: V4.1_WD01
>
>
> A client may want to group multiple data modification operations of a particular entity in a batch request and use ETags.  Currently, the client can use the ETag in the first data modification request but for all subsequent requests in the batch, it would have to use If-Match: *.
> We should allow the If-Match header to reference the ETag that resulted in a previous data modification request in a batch (similar to how we use the Content-ID to refer to the URI of an entity).



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