Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of zachary.zolton@gmail.com
 designates 209.85.218.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type
         :content-transfer-encoding;
        b=c2HvsYwWC9muderLpZ6GyxJ7cvcMbKagm9hC3QKV1GnO6xQk2qPW6IP1rqQ6NBeCzm
         UfYKneagDePp3H/xzxOenOiPXrh5SJyb9OlYPawpNAJcT7at0LRmfYhajYcxFupD6wrI
         jugSx20pMM+hpx7IxBtnhuYECUVN2odv9fhiE=
MIME-Version: 1.0
From: Zachary Zolton <zachary.zolton@gmail.com>
Date: Fri, 11 Sep 2009 12:28:26 -0500
Message-ID: <f728979f0909111028p76adbaabm58245db24c07cb8a@mail.gmail.com>
Subject: Varnish and Multi-doc Fetch?
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

I'm testing out using Varnish for my application, and so far most
everything "just works" with CouchDB. The only real problem I have is
that I'm using (probably abusing!) the multi-doc fetch feature, which
results in a POST request that Varnish isn't gonna cache.

(As an aside, I'm likely not properly de-normalizing my data=97since I'm
using the multi-doc fetch much like one would use SQL joins. I do plan
some big refactoring...!)

Two potential solutions I thought of:

1) Cache POST requests in my Varnish config=97this sounds like a can of
worms though, since POSTs can also be used for creating documents (not
to mention all the VCL-fu required)

2) Add a GET multi-doc fetch feature to CouchDB=97however, I'm guessing
there's a good reason why we don't already have this, right?  (^_-)

Anyways, I was wondering if anyone else has dealt with this situation
or has any ideas.


Cheers,

Zach