On Thu, Feb 12, 2009 at 10:01 PM, Brian Candler <[email protected]> wrote: > But I don't think this is currently exposed to the client. You'd need a > "wait until next fsync has completed" request, to let you know that it's > safe to send back a 250 OK to the client. >
I'm working on a project that plans to use replication and the update notification process to let clients know when a save is safely written to 2 nodes (ignoring fsync issues...) Write doc X to node A. Always be replicating to B. When doc X's new rev shows up on B, then you can tell the client it's been saved. -- Chris Anderson http://jchris.mfdz.com
