Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 57202 invoked from network); 26 Mar 2009 19:33:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Mar 2009 19:33:20 -0000 Received: (qmail 55549 invoked by uid 500); 26 Mar 2009 19:33:19 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 55471 invoked by uid 500); 26 Mar 2009 19:33:19 -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 55461 invoked by uid 99); 26 Mar 2009 19:33:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Mar 2009 19:33:19 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [89.16.178.93] (HELO server1.example.com) (89.16.178.93) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Mar 2009 19:33:11 +0000 Received: by server1.example.com (Postfix, from userid 65534) id 150641C8419; Thu, 26 Mar 2009 19:32:50 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on timparkin.vm.bytemark.co.uk X-Spam-Level: Received: from [192.168.1.6] (cpc1-leed1-0-0-cust606.leed.cable.ntl.com [81.102.230.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server1.example.com (Postfix) with ESMTPSA id 509B51C8416 for ; Thu, 26 Mar 2009 19:32:36 +0000 (GMT) Message-ID: <49CBD853.8020006@timparkin.co.uk> Date: Thu, 26 Mar 2009 19:32:35 +0000 From: Tim Parkin User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: dev@couchdb.apache.org Subject: Re: Restricting user interactions to a single document -- was [VOTE] Apache CouchDB 0.9.0 release References: <20090324140050.GA17574@tumbolia.org> <49C9776E.1060804@timparkin.co.uk> <49CA1307.7060300@timparkin.co.uk> <49CA2879.3070502@timparkin.co.uk> <49CA99A8.2060407@timparkin.co.uk> <3AC4FEF0-B2D6-4236-BB1F-73FB429584C8@apache.org> In-Reply-To: <3AC4FEF0-B2D6-4236-BB1F-73FB429584C8@apache.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 Damien Katz wrote: > Can you put your use case on the wiki? It would be helpful to start a > page about transaction use cases and where they are appropriate and the > downsides of using them. I'm thinking add something to describes you use > case and how it works (or doesn't work) with the current model, and also > the conflict checking transaction model. We might figure out new > solutions, tweaked models, etc that work better, or we might see the > pressing need for the transaction style. > > -Damien > Thanks Damien, Really appreciate the response.. I'll get stuff written up and have something the wiki for Monday.. Cheers tim