Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Sat, 13 Oct 2012 10:09:03 +0000 (UTC)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <1699909455.41242.1350122943369.JavaMail.jiratomcat@arcas>
In-Reply-To: <1288826750.4181.1349413130466.JavaMail.jiratomcat@arcas>
Subject: [jira] [Resolved] (COUCHDB-1555) Let _list generate its own Etag
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Newson resolved COUCHDB-1555.
------------------------------------

    Resolution: Duplicate

Duplicate of COUCHDB-1422
                
> Let _list generate its own Etag
> -------------------------------
>
>                 Key: COUCHDB-1555
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1555
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: View Server Support
>    Affects Versions: 1.2, 1.3
>            Reporter: Stephane Alnet
>
> As described in COUCHDB-1155, if a _list function generates dynamic content that is not idempotent with regards to the parameters used by to generate the Etag, there is no valid way for that function to specify an alternate Etag.
> The present request is to allow such functions to either (a) send back an Etag header which will supersede the Etag header computed by the view server and will be used as the opaque Etag string of RFC2616 section 3.11 [1], or (b) allow the function to send back some value that will be combined with the other (existing) Etag parameters to compute the Etag header, or (c) send back a flag indicating that the Etag header should be computed based on the output of the function, not the regular Etag parameters.
> [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.11

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira