[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-43) No indicator for optimistic concurrency control on EntityType or EntitySet level
[ http://tools.oasis-open.org/issues/browse/ODATA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-43:
----------------------------
Proposal:
Remove ConcurrencyMode facet attribute.
Define a new Behavior vocabulary with an annotation that expresses this meaning:
<Term Name="OptimisticConcurrencyControl" Type="Capabilites.OptimisticConcurrencyControlType" AppliesTo="EntitySet" />
<ComplexType Name="OptimisticConcurrencyControlType" Nullable="true">
<Documentation>
<Summary>If present, the annotated entity set uses optimistic concurrency control</Summary>
<LongDescription>If the ETag is computed from properties of entities of this set, these are listed in ETagDependsOn</LongDescription>
</Documentation>
<Property Name="ETagDependsOn" Type="Collection(Edm.Property" />
</ComplexType>
Accepted: https://www.oasis-open.org/committees/download.php/48411/odata-meeting-27_on-20130228-minutes.html#odata-43
Addendum: remove references to ConcurrencyMode from Part 1: Protocol, refer to Behavior vocabulary in ETag section
was:
Remove ConcurrencyMode facet attribute.
Define a new Behavior vocabulary with an annotation that expresses this meaning:
<Term Name="OptimisticConcurrencyControl" Type="Capabilites.OptimisticConcurrencyControlType" AppliesTo="EntitySet" />
<ComplexType Name="OptimisticConcurrencyControlType" Nullable="true">
<Documentation>
<Summary>If present, the annotated entity set uses optimistic concurrency control</Summary>
<LongDescription>If the ETag is computed from properties of entities of this set, these are listed in ETagDependsOn</LongDescription>
</Documentation>
<Property Name="ETagDependsOn" Type="Collection(Edm.Property" />
</ComplexType>
Accepted: https://www.oasis-open.org/committees/download.php/48411/odata-meeting-27_on-20130228-minutes.html#odata-43
Component/s: OData Protocol
> No indicator for optimistic concurrency control on EntityType or EntitySet level
> --------------------------------------------------------------------------------
>
> Key: ODATA-43
> URL: http://tools.oasis-open.org/issues/browse/ODATA-43
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData CSDL, OData Protocol , Vocabularies
> Affects Versions: V4.0_WD01
> Environment: [Proposed]
> Reporter: Ralf Handl
> Fix For: V4.0_WD01
>
>
> Currently the only way for a server to indicate to its clients that entities of a given type use optimistic concurrency control, and that the client thus has to watch out for ETags in responses and provide appropriate If-Modified headers in requests is to use the ConcurrencyMode="Fixed" facet on simple properties of an entity type.
> If the server
> - does not wish to disclose which properties it uses for optimistic concurrency control, or
> - does not include the concurrency control properties in the entity type, or
> - includes the properties as part of a complex type
> it has no means to advertise the presence of optimistic concurrency control to the client.
--
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]