From dev-return-10934-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue Jul 27 15:17:40 2010 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 33141 invoked from network); 27 Jul 2010 15:17:39 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Jul 2010 15:17:39 -0000 Received: (qmail 89019 invoked by uid 500); 27 Jul 2010 15:17:39 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 88940 invoked by uid 500); 27 Jul 2010 15:17:38 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 88925 invoked by uid 99); 27 Jul 2010 15:17:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jul 2010 15:17:38 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jul 2010 15:17:37 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o6RFHHLx004361 for ; Tue, 27 Jul 2010 15:17:17 GMT Message-ID: <27737564.25551280243837042.JavaMail.jira@thor> Date: Tue, 27 Jul 2010 11:17:17 -0400 (EDT) From: "Sebastian Cohnen (JIRA)" To: dev@couchdb.apache.org Subject: [jira] Commented: (COUCHDB-837) Adding stale=partial In-Reply-To: <2452653.8651280181143917.JavaMail.jira@thor> 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-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892815#action_12892815 ] Sebastian Cohnen commented on COUCHDB-837: ------------------------------------------ My first thought was something like: stale=ok&suppress_update=true (I like readable parameter names) But what about keeping stale=ok in its current form for backward compatibility and introduce a new parameter? stale=ok is somewhat understandable (and known), but combining it with this new behavior feels kind of odd to me. This would "free" the mindset and you don't need to construct a new parameter in addition to stale=ok or a new value for the stale param. And no, I don't have a good idea for a name for this case :) > Adding stale=partial > -------------------- > > Key: COUCHDB-837 > URL: https://issues.apache.org/jira/browse/COUCHDB-837 > Project: CouchDB > Issue Type: Improvement > Environment: all released and unreleased versions > Reporter: Filipe Manana > Assignee: Filipe Manana > Attachments: stale_partial.patch > > > Inspired by Matthias' latest post, at http://www.paperplanes.de/2010/7/26/10_annoying_things_about_couchdb.html, section "Views are updated on read access", I added a new value to the "stale" option named "partial" (possibly we need to find a better name). > It behaves exactly like "stale=ok" but after replying to the client, it triggers a view update in the background. > Patch attached. > If no one disagrees this isn't a good feature, or suggest a better parameter value name, I'll commit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.