On Feb 3, 9:40 pm, Roberto Spadim <robe...@spadim.com.br> wrote: > but like a sql server we can implement locks > with a key-value like we can implement locks...
There's no facility in memcached to create a reliable lock. You can't store anything you ever expect to get back. > with these three ideas we can have a very very good nosql server (it's > not a sql server yet, but it's very good) There are plenty of sql servers and nosql servers to choose from. > check that for a global locker (cluster) we don't have good > implementations (nfs have a locker daemon, some others file system > have, but a generic locker daemon don't exist (google answered to me > hehehe)) zookeeper, dlockd, elockd, old, about a million written in java, any webdav based web server, etc... Why don't you solve your problem with a tool designed to solve your problem? > CAS was not a core feature, but it's very nice to have CAS at server > side... why not a LOCK function? incr was also not a core feature at one point. It, and CAS have meaning in the scope of a cache since they're about manipulating data in a cache. It doesn't seem like you actually have a problem you're trying to solve.
