Details

Description

In the current implementation, there is no method for a non-CAS version of the append/prepend/incr/decr/add/replace operations. As per the memcached protocol, these operations do not require (but may be used with) a CAS id and requiring one greatly reduces the performance available by requiring a gets prior to the operation.

Raghavan Srinivas (Inactive)
added a comment - 22/Aug/12 11:00 AM The incr, decr, add and replace do have calls that do not require CAS Id. For the append and prepend methods
you could do something like this
c.prepend(0, "prepend-key", "value");
which would not require a CAS to be supplied/fetched. Will this suffice for now?
My suggestion would be to close this issue and open a separate issue for just append and prepend if it's still deemed a bug.

Michael, just to add here, I think it would be sufficient to document this rather than changing the API itself. Documenting that you can (and should!) pass 0 for the CAS value when using these operations.

Perry Krug
added a comment - 06/Feb/13 5:18 AM Michael, just to add here, I think it would be sufficient to document this rather than changing the API itself. Documenting that you can (and should!) pass 0 for the CAS value when using these operations.