Hi,

In the binary protocol, a client can send a DELETE request with a non- zero CAS.
The server should delete the item only if the CAS matches.
The release notes to memcached 1.4.0 specifically mention that CAS delete is now possible.
Memcached code clearly supports it.

But -- I'll refer here to http://code.google.com/p/memcached/wiki/BinaryProtocolRevamped --

In describing Set/Add/Replace, this spec explicitly tells the server to look at CAS. But in describing the Delete operation, the spec does not mention anything one way or another.

Also, the "binary delete" test in memcapable does not test for CAS delete.

It looks to me like the spec could be clarified, and memcapable is missing a test.

Does that sound correct?

Thanks,

JD


Reply via email to