[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1084) support optimistic locking with ETags and If-Match in rest server

[Trustin Lee (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee updated ISPN-1084:
------------------------------

    Fix Version/s: 5.1.0.BETA1
                   5.1.0.Final
                       (was: 5.0.0.FINAL)
                       (was: 5.0.0.CR3)


This is a new feature - should be scheduled for 5.1.

> support optimistic locking with ETags and If-Match in rest server
> -----------------------------------------------------------------
>
>                 Key: ISPN-1084
>                 URL: https://issues.jboss.org/browse/ISPN-1084
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cache Server
>    Affects Versions: 4.2.2.BETA1, 5.0.0.CR1
>            Reporter: Michal Linhard
>            Assignee: Trustin Lee
>             Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> currently it is not possible to do optimistic locking using the ETag feature in the REST server, because the "If-Match" HTTP header is ignored.
> We allow to put a value many times with the same "If-Match" header, but according to the spec:
> {quote}
> "A request intended to update a resource (e.g., a PUT) MAY include an If-Match header field to signal that the request method MUST NOT be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource. This allows the user to indicate that they do not wish the request to be successful if the resource has been changed without their knowledge. "
> {quote}
> (copied from http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.24)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira