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 paul.joseph.davis@gmail.com
 designates 209.85.214.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=biwhZZXKhwmmXoqLZ3w2VbmEjNylPy1uL2w2wwEqOF+1SSPsGHQlZKaAet8kM6YvyS
         SePOYCGwYFizEpVQrAcm8pPktkfyjUnsM6MV6JB7dRUektN1z2Sn+o6f2tSHTuXPOYuh
         witXSVnvILocP8fGuKj103eM8nQYC5LuCgTuM=
MIME-Version: 1.0
In-Reply-To: <ECCB220E-848C-480B-8B07-D8CAB23F63D5@utt.fr>
References: <1303324273.25024.1301.camel@dynamo>
 <DC03AF2B-87DD-45E8-AFC8-1E4859C684A4@utt.fr>
 <BANLkTinG5wTtx+QVAdEq45V4L2EovCtUuw@mail.gmail.com>
 <ECCB220E-848C-480B-8B07-D8CAB23F63D5@utt.fr>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Wed, 20 Apr 2011 16:20:01 -0400
Message-ID: <BANLkTinyW2C9_gQXcwX9=HudFuf_B2j=Cw@mail.gmail.com>
Subject: Re: JSON-Patch
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 20, 2011 at 3:59 PM, Aur=E9lien B=E9nel <aurelien.benel@utt.fr>=
 wrote:
> Dear Paul,
>
>> On the other hand, there's nothing inherently wrong with the PATCH verb
>
> True, PATCH could be idempotent... It just depends on your patch format.
>
> I just had a look at your patch operations specification:
> - When you add or remove a key/value, this is idempotent.
> - However, when you add or remove an array element based on an index, thi=
s is not.
>
>
> Regards,
>
> Aur=E9lien

Ah, fair point. I should've said there's nothing inherently wrong with
submitting a diff via POST (not PUT). And in fact RFC 5789 says that
PATCH is not safe or idempotent.

On the other hand, I have no idea how that has anything to do with
REST. Of specific note, Fielding himself calls out the PATCH verb as
an acceptable extension of the underlying protocol for a REST API [1].

[1] http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven