$batch: remove restriction "within the same change set " for Content-ID referencing

XMLWordPrintable

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

      Batch

    • Hide

      Remove restriction "within the same change set " for Content-ID referencing and allow referencing requests within the same batch that appear before the reference and thus already have been processed.

      Add term BatchContentIdReferencingAcrossChangeSetsSupported to Capabilities vocabulary, similar to the existing term BatchContentIdReferencingInRequestBodiesSupported.

      Show
      Remove restriction "within the same change set " for Content-ID referencing and allow referencing requests within the same batch that appear before the reference and thus already have been processed. Add term BatchContentIdReferencingAcrossChangeSetsSupported to Capabilities vocabulary, similar to the existing term BatchContentIdReferencingInRequestBodiesSupported.
    • Hide

      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx
      https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/vocabularies/Org.OData.Capabilities.V1.xml

      Show
      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/vocabularies/Org.OData.Capabilities.V1.xml

      Currently we restrict content-id referencing to entities created within the same change set. As we define that the content-id must be unique within a batch request, this is unnecessary.

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

              Created:
              Updated:
              Resolved: