[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1168) Clarify the use of ETags for Avoiding Update Conflicts
Evan Ireland created ODATA-1168: ----------------------------------- Summary: Clarify the use of ETags for Avoiding Update Conflicts Key: ODATA-1168 URL: https://issues.oasis-open.org/browse/ODATA-1168 Project: OASIS Open Data Protocol (OData) TC Issue Type: Bug Components: Protocol Affects Versions: V4.0_OS Reporter: Evan Ireland Priority: Minor http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Data_Modification states: 11.4.1.1 Use of ETags for Avoiding Update Conflicts If an ETag value is specified in an If-Match or If-None-Match header of a Data Modification Request or Action Request, the operation MUST only be invoked if the if-match or if-none-match condition is satisfied. The ETag value specified in the if-match or if-none-match request header may be obtained from an ETag header of a response for an individual entity, or may be included for an individual entity in a format-specific manner. Issue requiring clarification: we carefully need to distinguish between OData’s meaning of “entity = an instance of an entity type" and HTTP’s meaning of “entity = the thing whose representation is transferred”. ETags (= entity tags) refer to the HTTP meaning, and thus links/references/relationships are “HTTP entities” that can have their own ETags. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]