IETF Logo Mail Archive

Re: [apps-discuss] JSON Patch

Martin Thomson <martin.thomson@gmail.com> Tue, 22 November 2011 23:10 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C58321F85CE for <apps-discuss@ietfa.amsl.com>; Tue, 22 Nov 2011 15:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ovbj9jtCORzf for <apps-discuss@ietfa.amsl.com>; Tue, 22 Nov 2011 15:10:07 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5F95821F85B8 for <apps-discuss@ietf.org>; Tue, 22 Nov 2011 15:09:08 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so464640bkb.31 for <apps-discuss@ietf.org>; Tue, 22 Nov 2011 15:09:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qnxYUo7njc+3HN50u+aOkrNunpXNU0hlyum7XLQvkRQ=; b=wjKlFlVRtp2d66xZqyEXjT88jhOAWucRtKwrB7ZJIu6H0ngSHBH/r/H/RfhfHC0+yz TWMs2kDzgjmrXJs7pf9I8Ut7+v+JaL1hY+w0RfC3RNU8yYuiiUad7/UKBjKIE2uW+i83 +lltKatcdthMywm2uNKZRH7NvFPZsicKhMGcI=
MIME-Version: 1.0
Received: by 10.204.14.208 with SMTP id h16mr20750243bka.2.1322003346618; Tue, 22 Nov 2011 15:09:06 -0800 (PST)
Received: by 10.204.72.210 with HTTP; Tue, 22 Nov 2011 15:09:06 -0800 (PST)
In-Reply-To: <4ECBE991.9040704@gmx.de>
References: <4EB1482E.1040600@adobe.com> <4EB14C2E.8040208@gmx.de> <1320254564.2622.37.camel@neutron> <4EBBA0DD.9020605@gmx.de> <4ECBC843.60900@gmx.de> <1321986297.2091.1.camel@neutron> <4ECBE991.9040704@gmx.de>
Date: Wed, 23 Nov 2011 10:09:06 +1100
Message-ID: <CABkgnnVNWY0XxXRr+u5_PEyw_dse5bPMkYm0bzy-MdSTmyoqHA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="UTF-8"
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] JSON Patch
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 23:10:26 -0000

On 23 November 2011 05:27, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 2011-11-22 19:24, Paul C. Bryan wrote:
>> Looks good to me. I don't think "end" is needed, as the end index can be
>> explicitly specified.

I don't see there being much value either.

> It might make it easier to move something to the end when you don't know the
> whole array (for instance, because there may be race conditions)... Not sure
> how important that is for this use case, though...

I don't like the idea that you could be designing for race conditions
like that. Use conditional requests (thinking HTTP) or some form of
locking if it really must be at the end.

--Martin

v2.23.0 | Report a Bug | By Email