[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-274) OData clients should always use PATCH, deprecate PUT
[ http://tools.oasis-open.org/issues/browse/ODATA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Pizzo updated ODATA-274:
--------------------------------
Proposal:
State that Servers that support update MUST support PATCH, and clients SHOULD always use PATCH to update entities.
Servers MAY additionally support PUT, but should be aware of the possibility for data loss in round tripping.
Motion from 2013-3-7: Resolve ODATA-274 as proposed, with the additional clarification from comments that the listed additive changes should be allowed without versioning the service and that clients should be prepared to be resilient to such changes.
was:
State that Servers that support update MUST support PATCH, and clients SHOULD always use PATCH to update entities.
Servers MAY additionally support PUT, but should be aware of the possibility for data loss in round tripping.
> OData clients should always use PATCH, deprecate PUT
> ----------------------------------------------------
>
> Key: ODATA-274
> URL: http://tools.oasis-open.org/issues/browse/ODATA-274
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData Protocol , OData URL Conventions
> Affects Versions: V4.0_WD01
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Priority: Critical
> Fix For: V4.0_WD01
>
>
> PUT semantics call for setting to null any properties not specified in the payload. PATCH semantics apply the specified properties but leave unspecified properties unchanged.
> Specifying that clients ALWAYS use PATCH for updates is much safer for round-tripping data. For example, open properties, aggregated values, additive schema changes, and computed projections could all add additional properties to the payload that the client should be able to safely ignore. If the client uses PATCH to update then they do not lose information, but if the client ignores properties and uses PUT to update they will likely lose data in round-tripping.
> OData clients should always use PATCH when doing updates.
--
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]