[OASIS Issue Tracker] Commented: (ODATA-43) No indicator for optimistic concurrency control on EntityType or EntitySet level

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32525#action_32525 ] 

Ralf Handl commented on ODATA-43:
---------------------------------

Core is fine for me, as long as we get rid of the ConcurrencyMode attribute in CSDL.

> 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 v4.0
>    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