@antirez: What i'm missing now is a function on (n) slave that tells me whether one is up to date or not. Example: 1 - client 1 set foo,bar to node 1 2 - nod

@antirez: What i'm missing now is a function on (n) slave that tells me whether one is up to date or not. Example: 1 - client 1 set foo,bar to node 1 2 - node 2 replicates the data 3 - client 2 set foo,baz to node 1 4 - node 2 replicates the data What if a read (get foo) reaches node 2 between step 3 and 4? What's the return value? "bar" or "baz"? It would be nice if this kind of consistency can be done with redis... however... great work!!