IETF Logo Mail Archive

Re: [Jmap] draft-murchison-jmap-websocket as a JMAP working product

Ken Murchison <murch@fastmailteam.com> Fri, 23 November 2018 12:45 UTC

Return-Path: <murch@fastmailteam.com>
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 B931D128766 for <jmap@ietfa.amsl.com>; Fri, 23 Nov 2018 04:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=TLZpcuaa; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ECw0VDBv
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 Jl_OlTiSlttN for <jmap@ietfa.amsl.com>; Fri, 23 Nov 2018 04:45:00 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E6B124D68 for <jmap@ietf.org>; Fri, 23 Nov 2018 04:45:00 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id EEA7D22131; Fri, 23 Nov 2018 07:44:58 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 23 Nov 2018 07:44:58 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=subject:from:to:cc:references:message-id :date:mime-version:in-reply-to:content-type; s=fm1; bh=R9OsdfOnN EX8qliVG25ghXTJDBEWTHcPP4lQxhB1aF0=; b=TLZpcuaaa6CGJ5Lmii9ZJWodW utV0iOLSEtbLl8UhnBXPtzbez1XqwGmg3HhLO6//foG6FKRsYf5dYZ+zQExGdIK7 i4cxdCEd9WWSewP5Lvuiq+iLOW6y1pRJwiwMPJ4U18eQVPYAe3/NkQIMF+7jD+LI GlJnNuSXu5ashbfBiLDSqD61Qh2Otoj4Fanwl/24/t/T/5ey5LHrTCNzxCP74PkX IbbNZu3aGH2Ugcev+WmzTGw7nkfuRLznDnhGX02b12Ksqc0UAyXLvmuTI4M5qtrn rEYQxXJLhN9hy0nkG0t38+0KPtmjpc9bi82kUYMbRoTRNtHzNjMXXnMqux4NA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=R9Osdf OnNEX8qliVG25ghXTJDBEWTHcPP4lQxhB1aF0=; b=ECw0VDBvgTiIIaIyp9MkHh XNL9FxrGyXOlWwIl8JMLmJK3E2aPnTa5tyYxn1n4cZPbubwpHETjPquEptuJ+9lZ ptNWwAIWKmV1cgfUKPsE+qaezJLVAiheDcfsSjPfDuNnVgTJh2Bomqd1EyvmrJt0 FGgYuzp38VwLh5sfXyXzhH2Yyb8AYHkXbfr66X/DpqQL11xNshLsy3XZYGC/Oubq lhSnL4Z62LUH1VmCnMAMcTXiJ8UpzMzQEhf4iwjR3grhkwfetModMuSA2bn54pAS djWISBS8Cq02lFga0V5eIWFvn2gdwJAZiQzaK0yaXycUJj95pDfiutRHUZIn3mlg ==
X-ME-Sender: <xms:Svb3W6sEw_-bz8J138ozrLRIl7H8frkw34WzZ4DhHXKZa3P438wB9w>
X-ME-Proxy: <xmx:Svb3WykxUTAJSBHaMJWQMCHU3HVKj5ljuSEMQX7HJx0OiO1UG721aQ> <xmx:Svb3W3OcpsAV5U_kOO18Psgu1d2O09FdWC_QzDJfAlDibqV6XlZ3fA> <xmx:Svb3W39mhoTx2aiOIzX4KCa6PFhv0q05BqGU3s3euX90nwQ9_Pw47w> <xmx:Svb3WxEnJGDnfuI5a0A205ilmpQWKajdqq7AcpAactD8WDAnojNe4g> <xmx:Svb3W-j4m-598oK72xbBwGsdROl64Emsp_EAw_S9uLPeIrae8OcPnQ> <xmx:Svb3WyJqQA1rLWQedCodyeYXIteLhLYd74P5fU9pW_FZH6qVxcxhjA>
Received: from localhost.localdomain (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E6F5102A0; Fri, 23 Nov 2018 07:44:58 -0500 (EST)
From: Ken Murchison <murch@fastmailteam.com>
To: Neil Jenkins <neilj@fastmailteam.com>
Cc: IETF JMAP Mailing List <jmap@ietf.org>
References: <CALaySJLQV8U4P7nk97nVtRz7boArQ0F-dU0B7XYpN8wrfPsMpg@mail.gmail.com> <265ec3f1-75b8-43e3-8c52-276b6f6077c6@sloti7d1t02> <262a4f53-9f8c-b07d-eeb1-df1f77712f7c@fastmailteam.com>
Organization: FastMail US LLC
Message-ID: <b24af655-55d2-d86c-a71b-bbcb2748fcd1@fastmailteam.com>
Date: Fri, 23 Nov 2018 07:44:58 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <262a4f53-9f8c-b07d-eeb1-df1f77712f7c@fastmailteam.com>
Content-Type: multipart/alternative; boundary="------------4EC3B19C51AA5A1C47712D42"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/E81EvrbG1AYbvCC6jsHPGHWLZqo>
Subject: Re: [Jmap] draft-murchison-jmap-websocket as a JMAP working product
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: Fri, 23 Nov 2018 12:45:03 -0000

On 11/23/18 7:38 AM, Ken Murchison wrote:
>
>
> On 11/23/18 12:56 AM, Neil Jenkins wrote:
>> We also discussed the open issues at the JMAP session in IETF 103:
>>
>>
>>>    o  Should we allow out of order processing of requests?
>>
>> Again the consensus was "yes"; you can use a single WebSocket 
>> connection as the equivalent to parallel HTTP API requests. This 
>> means we also need an |id| property on Request and Response objects 
>> so they can be correlated by the client.
>
>
> Should we make this "requestId" to be a little more descriptive?  Or 
> perhaps steal "tag" from IMAP?
>

Is "clientId" in the request not sufficient for correlation?



-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC

v2.23.0 | Report a Bug | By Email