couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Truemper <>
Subject Re: potential conflict resolution strategy
Date Fri, 13 Nov 2009 22:10:25 GMT

> suppose i had an arbitrarily load-balanced front-end web server environment.
> a user throughout the lifetime of their session may get bounced to any of N
> different web servers, all talking to the same couch instance (for
> argument's sake). if these web servers are doing any kind of local caching
If you want to cache the documents, why not use a Squid in front of the CouchDB?

But for the argument: you should probably at least do a HEAD request to get the document's
ETAG, i.e. revision in order to avoid creating conflicts in you local cache...

View raw message