Re: [Jmap] new JMAP server for prototyping

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Mon, 24 May 2021 15:54 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF983A2DB0 for <jmap@ietfa.amsl.com>; Mon, 24 May 2021 08:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqQ7p0WFmVPS for <jmap@ietfa.amsl.com>; Mon, 24 May 2021 08:54:49 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41EE73A2D8A for <jmap@ietf.org>; Mon, 24 May 2021 08:54:48 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 5E96AC0051; Mon, 24 May 2021 17:02:43 +0100 (IST)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=none smtp.mailfrom=arnt@gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1621872163; bh=mBlQ3DzqCaC0n71IjO8y+mbzuG0gtu3EA3aO314rLiQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=CdLi0FeYESGkz51xLP8va4d/mQck8bHwKAMAYc6STS0Nh8YGVGMXamQ+HnR6wGiqp 1aFNlg2bKgFA0qOdTyoMlrAEGmlaausDdfpuw7rUkeczcaYoxk/L2/bW/8GZvlIwcj lPrbh0Y9l/P2dO9asVSYDRH2nTbzQ8pdu/OR0xYI=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1621872162-14925-14922/9/7; Mon, 24 May 2021 16:02:42 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: jmap@ietf.org
Date: Mon, 24 May 2021 17:54:42 +0200
Mime-Version: 1.0
Message-Id: <9eaa7a95-3959-4c5f-afb3-508bd97acbd3@gulbrandsen.priv.no>
In-Reply-To: <2fc30015-792a-4545-be1b-49257fec6481@beta.fastmail.com>
References: <20210521202012.GC7261@eh> <2fc30015-792a-4545-be1b-49257fec6481@beta.fastmail.com>
User-Agent: Trojita/0.7; Qt/5.11.3; xcb; Linux; Devuan GNU/Linux 3 (beowulf)
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/0r-Vep4s-wVn1K0g9l0mscHdUEQ>
Subject: Re: [Jmap] new JMAP server for prototyping
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2021 15:54:55 -0000

On Monday 24 May 2021 06:59:02 CEST, Neil Jenkins wrote:
> Technically it could destroy a creation in the same request 
> (it's a weird edge case, but it was worded that way 
> deliberately); I know we actually came across this scenario at 
> some point, although I can't remember why just now.

It seems like a reasonable enough combination when a mobile device leaves 
airplane mode and a mobile client is playing back stored actions.

Arnt