On Sep 4, 2007, at 21:35, [EMAIL PROTECTED] wrote:
- asynchronous repliacation. (like MySQL)
- single master, single slave.
- slave connect to master.
- sequence:
- client requests SET command to master
- push key to queue
- pop key from queue (asynchronous)
- fetch value for key
- send key/value to slave by memcached protocol
- when new slave connect to master, master copy whole data to slave.
Doesn't this mean that you will sometimes write a value to a cache,
and then later read a value back and get something other than the
latest value you wrote? Getting known stale values seems worse than
not getting something from the cache.
--
Dustin Sallings
