You could put nginx or another proxy server in front of couchdb and use http expires tags for your caching
On Fri, Nov 13, 2009 at 5:32 PM, Alex P <[email protected]> wrote: > i want to avoid the round trip if possible, hence the local cache. i'm not > worried about race conditions because i don't have multiple users accessing > the same data, so the only possible conflict scenario is being bounced to a > different server... > > On Fri, Nov 13, 2009 at 4:10 PM, Daniel Truemper <[email protected] > >wrote: > > > Hi, > > > > > 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... > > > > Daniel >
