Hello, Michal,
you will need some kind of cache invalidation. When you change the
data
in CouchDB, your application will have to notify Varnish the document
has changed and should purge it form the cache.
well, that's certainly doable, but I would rather not mess with cache
invalidation -- that'd bring a whole different layer in the stack.
Or, if you don't care Varnish will serve stale version of the
document,
you can cache it for some short period without the invalidation.
Yes, that's an approach we could use for certain resources, but not
ideal for most.
I am still curious if Varnish use ETag based caching at all?
It seems that Squid also does not work with ETags (http://wiki.squid-cache.org/Features/EtagSupport
). Can someone please clarify this?
The only info I've found is this old thread:
http://lists.varnish-cache.org/pipermail/varnish-misc/2008-November/002184.html
Thanks,
Karel
_______________________________________________
varnish-misc mailing list
[email protected]
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
