Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates
 209.85.198.247 as permitted sender)
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:x-mailer:mime-version:subject:date
         :references;
        b=nZveVo6sW4S/ZBIuF/Gww6z2xpt2zVSKz6txrsoXsuLYvGVsLsKRX7yGIbZQdyg7MH
         sK3rmXVQ59HgNf/ueCfQqNNgp2lFteKjYPWGSyOLfEfUQrM46mqdNSeo3iodi2IjFagT
         fJQ3b/iZzJw0kcIq5LECanu1/PmWzjbsXdWyk=
Message-Id: <A1F66502-5503-409D-8FCF-77B57B792A6F@gmail.com>
From: Chris Anderson <jchris@gmail.com>
To: couchdb-user@incubator.apache.org
In-Reply-To: <948486CF-C31A-4632-8890-3DC46CA57093@gmail.com>
Content-Type: text/plain;
	charset=us-ascii;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 5G77)
Subject: Re: partial/diff updates?
Date: Thu, 27 Nov 2008 16:06:29 -0800
References: <41DF7DCF-E050-4A02-B6C6-100787592E2D@gmail.com>
 <492E43E1.6010501@silencegreys.com> <20081127095830.GF6930@tumbolia.org>
 <D788352E-877D-480E-81AD-18459DE121D6@gmail.com>
 <20081127114016.GH6930@tumbolia.org>
 <48E899BC-96E0-4528-BF65-DB0A52998E91@gmail.com>
 <dba094300811270859n163de3d6h54070300af40b931@mail.gmail.com>
 <948486CF-C31A-4632-8890-3DC46CA57093@gmail.com>

The question becomes why not just use seperate docs?

Sent from my iPhone

On Nov 27, 2008, at 1:38 PM, Antony Blakey <antony.blakey@gmail.com>  
wrote:

>
> On 28/11/2008, at 3:29 AM, Timo Isokoski wrote:
>
>> Is this talk about the "diff" feature related to
>>
>> a) How CouchDB physically stores the data on disk
>> b) How data is transmitted between the client and CouchDB
>>
>> In case a) I think diffs are the devil and it goes aganist the  
>> simplicity of
>> CouchDB:s inner workings. In case b), wouldn't it be easy to  
>> implement some
>> kind of a prototype of this feature as a "proxy server" on top of  
>> CouchDB.
>> The proxy could route the normal requests directly to CouchDB and  
>> the actual
>> diff requests could be handled like this:
>> 1. GET the original document from Couch
>> 2. Apply diff
>> 3. PUT the modified document back to the Couch
>>
>> The functionality can then be integrated into CouchDB inself if the
>> prototype works well and and people start using it.
>
> It's case b. Integrating it with CouchDB to test it isn't that  
> difficult - certainly not difficult enough to justify implementing  
> it as a separate proxy, which IMO would involve lots of unnecessary  
> scaffolding.
>
> Those 3 steps are exactly what you would do as a plugin/extension.
>
> I think that any real-world application that justifies partial  
> updates probably also justifies partial gets, and not just a single  
> access path selection.
>
> Antony Blakey
> -------------
> CTO, Linkuistics Pty Ltd
> Ph: 0438 840 787
>
> There are two ways of constructing a software design: One way is to  
> make it so simple that there are obviously no deficiencies, and the  
> other way is to make it so complicated that there are no obvious  
> deficiencies.
>  -- C. A. R. Hoare
>
>