Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 83776 invoked from network); 4 Apr 2009 11:55:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2009 11:55:33 -0000 Received: (qmail 14817 invoked by uid 500); 4 Apr 2009 11:55:31 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 14721 invoked by uid 500); 4 Apr 2009 11:55:31 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 14711 invoked by uid 99); 4 Apr 2009 11:55:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 11:55:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of antony.blakey@gmail.com designates 209.85.142.190 as permitted sender) Received: from [209.85.142.190] (HELO ti-out-0910.google.com) (209.85.142.190) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 11:55:22 +0000 Received: by ti-out-0910.google.com with SMTP id u5so1608376tia.3 for ; Sat, 04 Apr 2009 04:54:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=JRn/K+ALcU6329QmkkzXQZw9cVeGgFYeCyXepLXA7hw=; b=AakKC8dmDyJsCIFcNKMsbMBKnkM+MWHaT6RTP0fnJiRrotz7ga6dLbWDd+W4djqUsH f1NRyp2eMnwWL8UplpVG747AE/AOnhQPWDXH9DRJph/br3MGPSUzcWJjoVHbwbDXRkxd 93TAEzYNFS5QKjeQcLroRE7EBUUHXCOxXHCWA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=e8fbZosPfLP+a7hdpig9CmHjelSZGmWtePwUOLndzE7QlX/zHIjM3T5Zku2wDppntD 2nnyxZSzxex3Oj3eunVU3vPxqVjEV1ySPENDL9B63364cVC4AdMvDpXztP7Me9X/PloQ 0+rFUYaPmLqiBusrzvlZcw3kNK2HB5Tnt8HGo= Received: by 10.110.7.5 with SMTP id 5mr3291415tig.13.1238846099932; Sat, 04 Apr 2009 04:54:59 -0700 (PDT) Received: from ?192.168.0.20? (ppp121-45-74-2.lns10.adl6.internode.on.net [121.45.74.2]) by mx.google.com with ESMTPS id j5sm4108306tid.21.2009.04.04.04.54.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Apr 2009 04:54:59 -0700 (PDT) Message-Id: From: Antony Blakey To: user@couchdb.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.4) Subject: Re: how to ensure transactions over multiple documents? Date: Sat, 4 Apr 2009 22:24:52 +1030 References: <49D61871.1090608@proven-corporation.com> <49D61D2B.7090600@proven-corporation.com> <49D62252.1050007@timparkin.co.uk> <49D62402.2010904@proven-corporation.com> <49D7206D.7010907@gmx.de> X-Mailer: Apple Mail (2.930.4) X-Virus-Checked: Checked by ClamAV on apache.org On 04/04/2009, at 9:48 PM, Andrius Juozapaitis wrote: > Antony: I was assuming (given a replication scenario) that I'll be > using one node as a master, and spring would only access this node > for updates, while the others would be used for reading only. Certainly for very specific architectures there are workable solutions - yours being one of them. My goal is to encourage the most general solution possible, as in my transactional git branch. If you eliminate relplication then you can completely wrap CouchDB's API and apply both significantly extended and quite different semantics (of course). In fact, this is how I think the app-server like features of CouchDB should be done, rather than the current model. The problem is that CouchDB doesn't expose enough to do that wrapping once replication is involved. Antony Blakey -------------------------- CTO, Linkuistics Pty Ltd Ph: 0438 840 787 Don't anthropomorphize computers. They hate that.