Correlate batch request and response parts via the Content-Id header

XMLWordPrintable

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

      [Closed]

    • Hide

      Clients SHOULD provide a Content-Id header for each request part as a header field of the multipart wrapper.

      Servers MUST copy the Content-Id header from a request part into the corresponding response part as a header field of the multipart wrapper.

      Show
      Clients SHOULD provide a Content-Id header for each request part as a header field of the multipart wrapper. Servers MUST copy the Content-Id header from a request part into the corresponding response part as a header field of the multipart wrapper.
    • Hide

      See ODATA-157

      Show
      See ODATA-157

      Currently the response to a batch request must contain the response parts in exactly the same order as the corresponding request parts.

      A more explicit correlation could be achieved by copying the Content-Id header from the request parts to the response parts, so clients providing this header could correlate the parts based on this header value.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: