[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-547) Clarify that the standard resources $id, $entity, $batch etc. win over content-id referencing
[ http://tools.oasis-open.org/issues/browse/ODATA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-547: ----------------------------- Proposal: See summary: standard resource cannot be "shadowed" by content-id referencing This change only removes doubt and does not add or remove a feature, so it is non-material. was: See summary: standard resource cannot be "shadowed" by content-id referencing We also might want to state whether batch requests can be nested within batch requests. > Clarify that the standard resources $id, $entity, $batch etc. win over content-id referencing > --------------------------------------------------------------------------------------------- > > Key: ODATA-547 > URL: http://tools.oasis-open.org/issues/browse/ODATA-547 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Batch Processing Format > Affects Versions: V4.0_CSD03 > Environment: [Proposed] > Reporter: Ralf Handl > Priority: Minor > Fix For: V4.0_CS02 > > > Content-id referencing uses the magic character $ followed by a token to refer back to a request that specifies that token in its content-id header. > Using one of the standard resource names without a $ prefix as a content-id could lead to confusion as URLs relative to the batch request URL are also relative to the service root and the relative URL for the standard resources thus starts with a $: > --batch_36522ad7-fc75-4b56-8c71-56071383e77b > Content-Type: application/http > Content-Transfer-Encoding:binary > Content-ID: batch > POST Customers HTTP/1.1 > <new customer body> > --batch_36522ad7-fc75-4b56-8c71-56071383e77b > Content-Type: application/http > Content-Transfer-Encoding:binary > Content-ID: nested-batch > POST $batch HTTP/1.1 > Content-Type: multipart/mixed;boundary=nested_batch_77162fcd-b8da-41ac-a9f8-9357efbbd > Content-Length: ### > --nested_batch_77162fcd-b8da-41ac-a9f8-9357efbbd > <content of nested batch > --nested_batch_77162fcd-b8da-41ac-a9f8-9357efbbd-- > --batch_36522ad7-fc75-4b56-8c71-56071383e77b-- > In this (admittedly weird) example the second POST request URL would not be interpreted as a content-id reference but literally as a request to $batch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]