Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-168

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

    XMLWordPrintable

    Details

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

      [Closed]

    • Proposal:
      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.
    • Resolution:
      Hide

      See ODATA-157

      Show
      See ODATA-157

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              handl Ralf Handl
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: