[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:comment-tabpanel&focusedCommentId=63369#comment-63369 ] 

Michael Pizzo commented on ODATA-541:
-------------------------------------

Do we need to introduce a new Etag-ID, or can we just use the same Content-ID header as the value for an Etag (the same as we do for a segment)?
Must the Etag be from the same changeset? Do we need to support a capability for cross-changeset etag usage?
Do we have a good use case scenario for this to use as an example? All of the cases I could come up with could be better addressed in 4.01.

Currently:
1) Re-used Content-ID for etag header as well, and
2) Did not restrict use to within the same changeset.

> 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: OData Protocol
>    Affects Versions: V4.0_CS01
>         Environment: Batch
>            Reporter: Matthew Borges
>            Assignee: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.01_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)