[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-42) 8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests
[ http://tools.oasis-open.org/issues/browse/ODATA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-42: ---------------------------- Proposal: If-None-Match:* with PUT is to restrict the UPSERT behavior to true INSERT. Necessary if ODATA-37 is accepted by the TC. Environment: [Proposed] > 8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests > ----------------------------------------------------------------------------------------- > > Key: ODATA-42 > URL: http://tools.oasis-open.org/issues/browse/ODATA-42 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Protocol v1.0 > Affects Versions: WD01 > Environment: [Proposed] > Reporter: Martin Zurmuehl > Fix For: WD01 > > > Use of If-None-Match with GET is clear: conditionally refresh caches. > Use of If-None-Match:* with PUT is to restrict the UPSERT behavior to true INSERT, for which OData already has POST ~/EntitySet, so this would just be an addition to ODATA-37. > Use of If-None-Match with an ETag value is unclear: it seems to be just a performance-optimized version of "ignore what other people told you and do what I tell you now". -- 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]