Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAD8rhfBaY8YsY_xHfbFWWVi1LbohxiJohWbF5sO+WsvOV2mRtA@mail.gmail.com>
References: <BANLkTintAR3bXwxPzx2tbpvdQUdRNc467A@mail.gmail.com>
	<A79B480392144A32ADEF9357EE0AF08B@rgabostyle.com>
	<BANLkTi=gU3n=VgA6EwwD1UvJOv0=f+SDQg@mail.gmail.com>
	<BANLkTikF=imZR05YKjKtBjY1LEBTMsR-zA@mail.gmail.com>
	<5CA42D48-AD47-4498-B30B-F3313216D447@apache.org>
	<BANLkTikas6b=187RgPUiyx5ZEQE8JGgQcQ@mail.gmail.com>
	<BANLkTi=sbsFzQoLbdA7TkspTqf91YiatgQ@mail.gmail.com>
	<BANLkTinB_W4mNGoPavjEL9zOpcNC7VBFvA@mail.gmail.com>
	<CAF4aNNi6_jfSoc2B06v3oL4PX4wJnsVjt8KPpOvyhBpRsy2oLg@mail.gmail.com>
	<CAD8rhfBnKW93v9jtHNaJbKFsA07=jt5+_nS+tuoC198Y-1Sv7A@mail.gmail.com>
	<CAF4aNNi_kEA9Sa_ZTTB+OJUSB8NrXEWCvgyqAi86gL5JrQF5Gg@mail.gmail.com>
	<CAF4aNNjxe1LZvcP70t=OYg6QB6CyCSPn288Y+bMbGqKbwHOQUg@mail.gmail.com>
	<CAD8rhfBaY8YsY_xHfbFWWVi1LbohxiJohWbF5sO+WsvOV2mRtA@mail.gmail.com>
Date: Mon, 12 Sep 2011 13:51:45 -0400
Message-ID: 
 <CALpjNy=ASaR9-mXAhnTq9ma_sccQB_buhhxwh0B7OC5nOwH8Hw@mail.gmail.com>
Subject: Re: Using couchdb for analytics
From: Sam Bisbee <sam@sbisbee.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Mon, Sep 12, 2011 at 1:27 PM, Scott Feinberg
<feinberg.scott@gmail.com> wrote:
> Unless you can ensure that only one process will be editing the document at
> a time (to ensure that you never end up holding an old revision), your going
> to have issues. I've never tried it, but I'd be under the assumption
> conflict resolution wouldn't work at all.

My favorite way for doing something like that is to use a queue. Your
app stores the analytics transactions in the queue and you have a
consumer that puts them into Couch at its own pace. If you want to do
so with a single thread, then go for it.

--
Sam Bisbee