Return-Path: 
 <dev-return-30324-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org>
X-Original-To: apmail-couchdb-dev-archive@www.apache.org
Delivered-To: apmail-couchdb-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 78D98104E0
	for <apmail-couchdb-dev-archive@www.apache.org>;
 Thu, 28 Nov 2013 14:37:07 +0000 (UTC)
Received: (qmail 58511 invoked by uid 500); 28 Nov 2013 14:36:51 -0000
Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org
Received: (qmail 58365 invoked by uid 500); 28 Nov 2013 14:36:38 -0000
Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@couchdb.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@couchdb.apache.org>
List-Post: <mailto:dev@couchdb.apache.org>
List-Id: <dev.couchdb.apache.org>
Reply-To: dev@couchdb.apache.org
Delivered-To: mailing list dev@couchdb.apache.org
Received: (qmail 58347 invoked by uid 99); 28 Nov 2013 14:36:36 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Nov 2013 14:36:36 +0000
Date: Thu, 28 Nov 2013 14:36:36 +0000 (UTC)
From: "Alexander Shorin (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12681774.1385648827993.44422.1385649396856@arcas>
In-Reply-To: <JIRA.12681774.1385648827993@arcas>
References: <JIRA.12681774.1385648827993@arcas>
Subject: [jira] [Commented] (COUCHDB-1942) Add info to the docs how Caching
 works in CouchDB (HTTP)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/COUCHDB-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834888#comment-13834888 ] 

Alexander Shorin commented on COUCHDB-1942:
-------------------------------------------

Hm...To be clear "how caching works" is not about configuration, but about how HTTP should work. So depending what topic you'd like to describe target article would be different. While IRC discussion was about proxy server configurations (as I fell it) the issue topic better fits to api/basics.rst where base HTTP things are described lightly.

> Add info to the docs how Caching works in CouchDB (HTTP)
> --------------------------------------------------------
>
>                 Key: COUCHDB-1942
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1942
>             Project: CouchDB
>          Issue Type: Documentation
>          Components: Documentation
>            Reporter: Andy Wenk
>            Assignee: Andy Wenk
>
> [15:14:21] <yawnt>	 hi
> [15:14:36] <yawnt>	 is it possible to cache couchdb using, for instance, varnish and etags?
> [15:14:44] <yawnt>	 all i can find on google is stuff that dates back 3 years :\
> [15:15:33] <+rnewson>	 yawnt: yes, we send ETag, etc.
> [15:15:47] <yawnt>	 because i read that varnish only supported etags in the frontend
> [15:15:52] <+rnewson>	 not much value in a cache for some operations, though.
> [15:15:54] <yawnt>	 and doesn't check in the backend
> [15:16:15] <yawnt>	 rnewson: in particular i'm talking about caching attachments
> [15:16:28] <+rnewson>	 competent http caching proxies will work in front of couchdb, I don't know varnish.
> [15:16:41] <+rnewson>	 caching attachments could be useful, sure.
> [15:16:44] <+rnewson>	 and view output
> [15:17:03] <yawnt>	 i guess i'll drop by in #varnish then
> [15:17:05] <+rnewson>	 anywhere where the staleness check is cheaper than the evaluation, basically.
> [15:17:05] <yawnt>	 thanks for your help :)
> [15:17:11] <yawnt>	 obviously!
> [15:17:29] <+rnewson>	 I wish it were obvious to more people, :)
> [15:17:51] <yawnt>	 haha yeah i suppose so
> [15:18:51] <yawnt>	 cache isn't dark magic :D
> [15:20:12] <+awenkhh>	 rnewson: maybe we could add some info about that in the docu although it's already an existing concept hwen using http?
> [15:21:34] <+rnewson>	 awenkhh: I guess we could expand on it, but, yeah, it's a standard 2616 thing.
> [15:22:16] <+awenkhh>	 rnewson: got an idea where a good place would be in the docs?
> [15:22:34] <+rnewson>	 none, sorry. I'm an avoider of documentation.
> [15:22:35] <+Kxepal>	 awenkhh: http://docs.couchdb.org/en/latest/config/proxying.html
> [15:23:07] <+Kxepal>	 thought it contains information how to use couchdb as proxy, I think it's good place about how to use proxies with couchdb too
> [15:27:09] <+Kxepal>	 awenkhh: from wiki we could get nginx and apache guides, but I could only advocate for nginx one since prefer to avoid apache completely (:



--
This message was sent by Atlassian JIRA
(v6.1#6144)