Hide Forgot
project_key: EDG I don't know whether this is a bug or a feature request (I'm no good at interpreting specifications) But we have a problem with this one: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.24 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}
I think this is both a bug and a feature request at the same time. If {{If-Match}}, {{If-None-Match}}, and other related headers are not supported yet, the server must respond with the {{501 Not Implemented}} status. Therefore, it's a bug in Infinispan's REST implementation if it does not respond correctly. Implementing optimistic locking is another story, and it should be implemented in Infinispan 5.1 since it's a new feature. Sounds OK?
OK so let this jira be about the bug and adding the proper 501 response. And I'll create a feature request for ISPN 5.1
Link: Added: This issue relates to ISPN-1084
Link: Added: This issue is related to ISPN-1098
Release Notes Text: Added: Infinispan 5.1.0.Alpha1 contains the fix for ISPN-1084
Release Notes Text: Removed: Infinispan 5.1.0.Alpha1 contains the fix for ISPN-1084