Re: [hybi] Straw poll: Do you miss interjectable WebSocket level control frame? (was: Re: Discontinuation of mux ...)

Ian Hickson <ian@hixie.ch> Wed, 26 February 2014 17:35 UTC

Return-Path: <ian@hixie.ch>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 788A11A00E8 for <hybi@ietfa.amsl.com>; Wed, 26 Feb 2014 09:35:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
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 DRRYAm9OcHyO for <hybi@ietfa.amsl.com>; Wed, 26 Feb 2014 09:35:11 -0800 (PST)
Received: from homiemail-a45.g.dreamhost.com (caibbdcaacfa.dreamhost.com [208.113.200.250]) by ietfa.amsl.com (Postfix) with ESMTP id D9A621A0074 for <hybi@ietf.org>; Wed, 26 Feb 2014 09:35:11 -0800 (PST)
Received: from homiemail-a45.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTP id BA7F3480D0; Wed, 26 Feb 2014 09:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=dPDqUcDW+ykRVL7plGasjA8nGF8=; b=yue /0v5MQQ8dtnpRUSSWy7LFOx5z4akem/rzh1aSXlly/Ymkjdobm01sM1SqailSPFa hMsZ3Yzyx8u1+9CMBwfT6ue8KSZf2KzEhR7MMul1K/ssx0CHKCTAfE+eGgQ8sNAA HpISYv/o4meEgO9UAbT2pAeSg+CIEJJeJCz+Osys=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [208.113.236.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTPSA id AA5B14809C; Wed, 26 Feb 2014 09:35:10 -0800 (PST)
Date: Wed, 26 Feb 2014 17:35:10 +0000
From: Ian Hickson <ian@hixie.ch>
To: Takeshi Yoshino <tyoshino@google.com>
In-Reply-To: <CAH9hSJbSfQ2Abp6oLifi0dx4TZENzm2QRn8zMQfAv=vw+H12sw@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1402261734120.31525@ps20323.dreamhostps.com>
References: <CAH9hSJbjQNKnZTJmBFtU8MgmnRTYjPopC4oP_78bWUGap-9CvA@mail.gmail.com> <CAH9hSJbBmvNPBSSAk-khdWXgWw0GTt0FG3KsdzYeJcfiAPDk0A@mail.gmail.com> <CAHixhFq=wfmYH8-ij_WtsQLN=NUTJwRQ=k8jCPepQDM8V8ZZYA@mail.gmail.com> <CABihn6EN7V6XEwf6NWn78orxvr3XjGHxROJC4JjQ6RYYKEeCug@mail.gmail.com> <CACuKZqHNoR5GQmWyzbXAszZCOT2P4pjSmT3SF6ZG3X7hTY=1xw@mail.gmail.com> <CABihn6GC4VM2AHza-F7ML=FfHLZu7FNqx+BhbuVsfJLWk0P92w@mail.gmail.com> <CAH9hSJbSfQ2Abp6oLifi0dx4TZENzm2QRn8zMQfAv=vw+H12sw@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/3jJY-6cTHtAY0Dd3ekKUcZlD2ZM
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] Straw poll: Do you miss interjectable WebSocket level control frame? (was: Re: Discontinuation of mux ...)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 17:35:16 -0000

On Wed, 26 Feb 2014, Takeshi Yoshino wrote:
> 
> I think it's underspecified. In the WHATWG WebSocket API spec, close() 
> is required to "start the WebSocket closing handshake". RFC 6455 neither 
> says the algorithm may terminate ongoing "Send a WebSocket Message" 
> algorithm nor says it may not.

If it doesn't allow it, then it's not allowed.

If you send a bunch of messages, then start the closing handshake, then 
the messages should all be sent. I don't think there's anything in either 
spec that would allow the handshake to jump ahead.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'