IETF Logo Mail Archive

Re: [Jmap] Fwd: New Version Notification for draft-murchison-jmap-websocket-00.txt

Brad Kowalczyk <brad@staff.atmail.com> Tue, 12 June 2018 03:10 UTC

Return-Path: <brad@staff.atmail.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 0FD5A130DE2 for <jmap@ietfa.amsl.com>; Mon, 11 Jun 2018 20:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-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=staff.atmail.com
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 585tvzIAgkCF for <jmap@ietfa.amsl.com>; Mon, 11 Jun 2018 20:10:15 -0700 (PDT)
Received: from staff72.atmail.com (staff72.atmail.com [204.145.97.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AB28130F0F for <jmap@ietf.org>; Mon, 11 Jun 2018 20:10:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=staff.atmail.com; s=20160330; h=Content-Type:MIME-Version:Date:Message-ID: From:To:Subject; bh=fUnguVrtUImHMtWEEFSfxSZIubkzaftYDQbH1eKWZHA=; b=VInBTzIRz wzUEOwyJJme69ZqcUi0Lzmm6RX1Y4c6cQsbT732cfhheY0YY9VQGGKJBLfRdt5CaiCuNxNR9QjR5t LxGMOJraDC3SiZTK6C2A82sqt4r01PQAesCUKIEzFRaZSnndY2sUuOlt7GBZKABZ4UbGtgcqnC+iM FA4Bbghk=;
Received: from 35.124.233.220.static.exetel.com.au ([220.233.124.35] helo=[172.16.254.117]) by hc0-dh-ro-aio-002.internal.atmailcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1) (envelope-from <brad@staff.atmail.com>) id 1fSZgo-00083m-Iq; Tue, 12 Jun 2018 13:09:47 +1000
To: Neil Jenkins <neilj@fastmailteam.com>, Dave Richards <dave.richards@staff.atmail.com>, Tom Smith <tom.smith@staff.atmail.com>
Cc: IETF JMAP Mailing List <jmap@ietf.org>
References: <f6e3576a-b5af-885e-6393-f1d3c8fb4cc9@staff.atmail.com> <305ecac4-d5cb-2935-a1ef-e3dcc6823e0f@fastmail.com> <42d9cdbc-338b-125b-4164-76dda81c81fa@fastmailteam.com> <152762434119.30187.891281157139219165.idtracker@ietfa.amsl.com> <113acf52-6b03-4914-a0f2-7fdf08b1cf98@sloti22d1t06> <32a1f0a3-6fb3-4858-82f9-abc27d526f82@sloti35d1t03> <4F1C8A0C-C3BA-454B-A85D-3AB37DAC12BE@staff.atmail.com> <31adb407-2673-4632-b936-74cbf1e4b861@sloti35d1t03>
From: Brad Kowalczyk <brad@staff.atmail.com>
Message-ID: <6dda42f4-3a48-10ca-e9c6-a48cfa6284e4@staff.atmail.com>
Date: Tue, 12 Jun 2018 13:10:08 +1000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <31adb407-2673-4632-b936-74cbf1e4b861@sloti35d1t03>
Content-Type: multipart/alternative; boundary="------------49D29ED80643FF8799B831A8"
Content-Language: en-US
X-Atmail-Id: brad.kowalczyk@staff.atmail.com
X-atmail-spam-CA-score: 0
X-atmail-spam-CA-bar: /
X-atmail-spam-CA-report: X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-Flags: 0 X-CTCH-RefID: str=0001.0A020212.5B1F3995.0061, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-atmail-spam-score: -189
X-atmail-spam-bar: -------------------
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/rVZnYA8Fp0RSLSUWzJ_--cW4RY8>
Subject: Re: [Jmap] Fwd: New Version Notification for draft-murchison-jmap-websocket-00.txt
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 12 Jun 2018 03:10:19 -0000

We use a separate URL

e.g. https://somedomain.com/events for SSE as opposed to 
https://somedomain.com/api for the core JMAP API

Cheers,

Brad

On 12/06/18 12:33, Neil Jenkins wrote:
> On Tue, 12 Jun 2018, at 10:13 AM, Tom Smith wrote:
>> No, we use Server Sent Events, as per the original spec.
>> https://www.w3schools.com/html/html5_serversentevents.asp
>
> That's an interesting data point in whether to send push events down 
> the websocket, but I think the question Dave was actually passing on 
> was this one:
>
>> Does anyone here have experience running an API that's available over 
>> either websockets or HTTP? If so, would you normally put the 
>> websockets upgrade on the same URL, or a different one? Making it 
>> separate certainly gives you more flexibility, so seems like the 
>> right option to me, but I'd be interested if anyone has real-world 
>> experience.
>
> Cheers,
> Neil.

v2.23.0 | Report a Bug | By Email