Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of antony.blakey@gmail.com
 designates 209.85.198.234 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:mime-version:subject:date:references
         :x-mailer;
        b=b2TB09ZhWG7/93IGecpGcbSVjKWGjJTUSKosKH7ankqO+qu4lXIvHPsBl/IubfRC5w
         DPKOWuafp7Ub/ZozS2MMuYPeco268TiByp9nKxLO+pBGy2ENS0V1TnoGy+aBLmHV98Ls
         o2EyE5MnbXwY9+BJwZXHgnt9/nVmNQncLLmaA=
Message-Id: <076DBF05-0133-4B52-A179-096FB4B6E244@gmail.com>
From: Antony Blakey <antony.blakey@gmail.com>
To: user@couchdb.apache.org
In-Reply-To: <77435695-5D71-4C35-922A-9434D69834D3@pobox.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: drill into a doc with a GET?
Date: Thu, 8 Jan 2009 21:58:39 +1030
References: <013C8232-C1A7-4C69-8996-21C86B41B340@koberg.com>
 <e2111bbb0901071824o3912f41fs9fce01e836afbe51@mail.gmail.com>
 <5F4CD013-AB8B-4570-8106-6DCE08FBA550@koberg.com>
 <e2111bbb0901071932p5b661b79se37d05c553d92a04@mail.gmail.com>
 <60226249-2781-43AF-86B8-17940B3B9251@koberg.com>
 <e2111bbb0901072108y2da592eapd9a461016b3333aa@mail.gmail.com>
 <B0070955-BAD2-43A3-B7C4-63A5DACE33E0@gmail.com>
 <77435695-5D71-4C35-922A-9434D69834D3@pobox.com>


On 08/01/2009, at 9:11 PM, Geir Magnusson Jr. wrote:

> Eh?
>
> 1) This is the *ideal* place to explore diff support.  JSON came  
> about because someone just did it and built things with it.

Totally agree.

> 2) Couch could easily support an update mechanism that would then be  
> deprecated once Real(TM) "JSON diff" support showed up.

I certainly don't want to write an RFC, but the condition was that  
partial updates wouldn't be considered unless it was an implementation  
of an RFC, and if an RFC existed, it would very likely be incorporated.

> Fantastic.  So why don't you both implement your ideas in Couch and  
> then let a broad spectrum of users w/ diverse applications test them  
> and give feedback?  That seems like the only way something sane can  
> come out.

Our disagreement was about the nature of the RFC - http://groups.google.com/group/json-diff/browse_thread/thread/595370127b665611 
.

AFAIK Noah wasn't planning to do an implementation, and without in- 
principle PMC agreement, it's not going to happen.

IMO there are more important, fundamental issues to deal with before  
CouchDB commits to a released API.

Antony Blakey
-------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787

It's amazing that the one side of the conversation that survived is "I  
don't know art, but I know what I like". The reply from the artist was  
"Madam, so does a cow".
   -- Carl Kirkendall