IETF Logo Mail Archive

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

Ken Murchison <murch@fastmailteam.com> Fri, 23 November 2018 15:05 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 D392F130E09 for <jmap@ietfa.amsl.com>; Fri, 23 Nov 2018 07:05:37 -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=k09LBbi/; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=uH70jHHP
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 Uidx5lwNB9xq for <jmap@ietfa.amsl.com>; Fri, 23 Nov 2018 07:05:36 -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 46399130DCE for <jmap@ietf.org>; Fri, 23 Nov 2018 07:05:36 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2DA9D220D8; Fri, 23 Nov 2018 10:05:35 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 23 Nov 2018 10:05:35 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=subject:to:cc:references:from:message-id :date:mime-version:in-reply-to:content-type; s=fm1; bh=uFWqqKxxH jtCLPNEV775HFNFdOvctueQsmk5BmhF684=; b=k09LBbi/SEKWsb1utV/FJyA45 sWHdKTnl5m8oMifl35eH0r5z+SUSV9eBYCR+XL+XepmX4KqUXmtOApnm1W8Cr2Dq QV2uqDVE8iNwgIF3As57vJd0d+PZRbk35hvjF249N5fPGdEs7asys3ODHu1027zP ScX2qjbamo3HvmbzbqdFxZoZRF+rT8rYuCunX0fJ9TmwQOBlQEyYqzmwoRNKOdRH ofkjr4lqW7Dgt53IBwNN7kI8/kY2Z4OD1IO0OmrvAFMglvylwEBNux44YPLzs+qG 6LtL/JvwvhkJlvGAoIQH0f0+usCJUmi+6TmKydWZCScDYBEUqsQg6Z/WxP82g==
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=uFWqqK xxHjtCLPNEV775HFNFdOvctueQsmk5BmhF684=; b=uH70jHHPn2ndrYfZLY2YuE YC+hLkaBryb2NeyYDNT95IEQ+Wa0CrvqCdpiV0EdeGf+XIxSOlFB1SbdA/VZ/SMf TZ0hh183/YaraJyjzOx8YGMF3Z7w6g0cuPF8LV6CEzf83TTdCxU1BKjMDDLwyLbB 2pcy6Bi5SdCkpeMxD7iJ79h97I+tNeZnfqld2rTA/H7nnICVLXxR2hnj89drMjmj ejnBO9uzAy9C+FD+NUG3FoCavE2DrS+int9cPwwrjObXg/kzLM5M+/dqJkKGkPwP heJUnKI/ZTbe4OWr7EPxCKBMPC9cMaGz38tW1KOgpLi69PukY4dIsRBDce4xKw6Q ==
X-ME-Sender: <xms:Phf4W-ZFopHVeju34Bj6YOefbWEFc4KuSYW30-JQPQxZxFObtp0QyA>
X-ME-Proxy: <xmx:Phf4W5zUUj_jnbI4fkh_7KeqAUhCp8hknDIRQAgnO31zcMLobGc_eA> <xmx:Phf4W_U90-0p7NlPsMDDDol4dMYQOY558664NbLkBrq53JwXvABxCw> <xmx:Phf4W2ngACERqxyDmFGW_JU-zj-pLy04opqjn47YyCpd2TvwIFjSOw> <xmx:Phf4Wzp6cPW2wdWmQZJ0Klq1JoqtGUNFnSZXC_MUR_fOOwAtlQIGSg> <xmx:Phf4W2s8nq3WcHZZ8Lx57ofN73jhQQ1oxP2UWaEVIBQFfa1TY7dRgA> <xmx:Pxf4W-g5RcLiDTyR4c2KJejdO4ZC6Fy-ge_mwMt2UynzUsc6H-nSUQ>
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 28673E49EC; Fri, 23 Nov 2018 10:05:34 -0500 (EST)
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>
From: Ken Murchison <murch@fastmailteam.com>
Organization: FastMail US LLC
Message-ID: <e1c4c556-691c-5ced-7dae-52930b2d9194@fastmailteam.com>
Date: Fri, 23 Nov 2018 10:05:33 -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: <265ec3f1-75b8-43e3-8c52-276b6f6077c6@sloti7d1t02>
Content-Type: multipart/alternative; boundary="------------00960547616EC984C0CAD7CB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/E6_fSS8q3Zj0W7edyskdw6l-zF8>
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 15:05:38 -0000

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 push notifications over the WS connection?
>
> The consensus in the room was "yes", we should use the connection we 
> already have. We would therefore need to:
>
>   * Add a tag to each JSON object sent through the socket so we know
>     what it is. I would suggest an |@type| property with values of
>     |"Request"| (sent by the client to the server), |"Response"| and
>     |"StateChange"| (sent by the server for API responses and pushes
>     respectively). (These are the names of the objects in the JMAP spec.)
>

Do we push ALL notifications or do we allow the client to subscribe to 
notifications for certain object types?


-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC

v2.23.0 | Report a Bug | By Email