Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_CS01
    • Component/s: Protocol
    • Environment:

      Batch

    • Hide

      Introduce a new header, ETag-ID. Allow the If-Match header value in batch requests to be $<ETag-ID> so that it can refer to the ETag that resulted from a previous data modification operation in the batch request. The '$' prefix would signal to the batch processor that the If-Match header value is a reference to a previous ETag, rather than an ETag literal.

      Show
      Introduce a new header, ETag-ID. Allow the If-Match header value in batch requests to be $<ETag-ID> so that it can refer to the ETag that resulted from a previous data modification operation in the batch request. The '$' prefix would signal to the batch processor that the If-Match header value is a reference to a previous ETag, rather than an ETag literal.
    • Show
      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx

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

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            Matthew Borges (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: