Re: [hybi] Clarify the role of closing handshake
Justin Lee <jlee@antwerkz.com> Tue, 15 February 2011 22:48 UTC
Return-Path: <jlee@antwerkz.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8A3C3A6C43 for <hybi@core3.amsl.com>; Tue, 15 Feb 2011 14:48:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.016
X-Spam-Level:
X-Spam-Status: No, score=-1.016 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2O2h1gaSgKbf for <hybi@core3.amsl.com>; Tue, 15 Feb 2011 14:48:41 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 2BB7C3A6A3D for <hybi@ietf.org>; Tue, 15 Feb 2011 14:48:41 -0800 (PST)
Received: by fxm9 with SMTP id 9so839594fxm.31 for <hybi@ietf.org>; Tue, 15 Feb 2011 14:49:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.74.5 with SMTP id s5mr3256800faj.72.1297810146924; Tue, 15 Feb 2011 14:49:06 -0800 (PST)
Received: by 10.223.10.144 with HTTP; Tue, 15 Feb 2011 14:49:06 -0800 (PST)
In-Reply-To: <AANLkTin+5mxtbD4GbNK1X2P3CEyLQngOB06qj9sN-Gjh@mail.gmail.com>
References: <4D5AE318.9080308@stpeter.im> <OF9E69202E.36384265-ON88257838.00749E83-88257838.007782CA@playstation.sony.com> <AANLkTin+5mxtbD4GbNK1X2P3CEyLQngOB06qj9sN-Gjh@mail.gmail.com>
Date: Tue, 15 Feb 2011 17:49:06 -0500
Message-ID: <AANLkTimpa0A8UbS-N+d2NsHzYyCibvq9TXyDF9yZaT14@mail.gmail.com>
From: Justin Lee <jlee@antwerkz.com>
To: hybi@ietf.org
Content-Type: multipart/alternative; boundary="20cf3054a38fcb1a4d049c59f8cc"
Subject: Re: [hybi] Clarify the role of closing handshake
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 15 Feb 2011 22:48:43 -0000
On Tue, Feb 15, 2011 at 5:45 PM, Takeshi Yoshino <tyoshino@google.com>wrote: > On Tue, Feb 15, 2011 at 13:45, <Yutaka_Takeda@playstation.sony.com> wrote: > >> >> Okay, I admit my example was bad. >> >> Just to be clear, even with this code: >> >> websocket.send("a-message-needs-to-reach-server") >> websocket.close() >> >> From your opinions, programmers should not expect that the message always >> reach the server. (granted) >> >> > Yes, this point should be noted in the spec, or developers may > misunderstand. > In the grizzly version, I actually just queue up the close frame behind the others. Is this not what should happen? Should the close frame jump to the front of the line? > > >> Now, here's another question for you. >> >> If onclose() callback is made on the websocket, would it be helpful if >> that callback (with wasClean=true) guarantees >> that the message has been delivered to the server? >> >> > Just to be sure, again I'd like to note that ... the complex algorithm in > -05 realizes this (wasClean=true iff received Close frame with "C"), but any > of the proposal A-1, A-2, B I wrote don't. What A-2 and B can do is just > avoiding RST hazard case. > > >> # trying to figure out whether graceful shutdown at least during 'closing' >> state would ever be helpful. >> >> > I personally think since an application can have its own ack to take care > of this, we don't have to have this feature as mandatory in WebSocket. > > >> Thanks, >> - Yutaka >> >> >> hybi-bounces@ietf.org wrote on 02/15/2011 12:33:28 PM: >> >> >> > On 2/15/11 1:30 PM, Brian wrote: >> > >> > > If you need, with websocket, to detect that the user's gone >> > > away (such as for an IM system to show that they're offline), you can >> > > do that on the server when you detect the connection is closed. If >> > > you're using xhr-polling or similar, a reasonably short timeout on the >> > > server during which the user doesn't reconnect for more data should >> > > suffice as a suitable "user has gone away" event. >> > >> > Agreed. And this is what we do in IM systems like XMPP (whether using >> > the TCP binding or BOSH). >> > >> > Peter >> > >> > -- >> > Peter Saint-Andre >> > https://stpeter.im/ >> > >> > >> > >> > [attachment "smime.p7s" deleted by Yutaka Takeda/R&D/SCEA] >> > _______________________________________________ >> > hybi mailing list >> > hybi@ietf.org >> > https://www.ietf.org/mailman/listinfo/hybi >> >> _______________________________________________ >> hybi mailing list >> hybi@ietf.org >> https://www.ietf.org/mailman/listinfo/hybi >> >> > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > > -- You can find me on the net at: http://antwerkz.com http://www.linkedin.com/in/justinlee http://www.twitter.com/evanchooly
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Gabriel Montenegro
- [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake John Tamplin
- Re: [hybi] Clarify the role of closing handshake Greg Wilkins
- Re: [hybi] Clarify the role of closing handshake Gabriel Montenegro
- Re: [hybi] Clarify the role of closing handshake Greg Wilkins
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Brodie Thiesfield
- Re: [hybi] Clarify the role of closing handshake Gabriel Montenegro
- Re: [hybi] Clarify the role of closing handshake Greg Wilkins
- Re: [hybi] Clarify the role of closing handshake Brodie Thiesfield
- Re: [hybi] Clarify the role of closing handshake Salvatore Loreto
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Gabriel Montenegro
- Re: [hybi] Clarify the role of closing handshake Andy Green
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Gabriel Montenegro
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake John Tamplin
- Re: [hybi] Clarify the role of closing handshake Brian
- Re: [hybi] Clarify the role of closing handshake Peter Saint-Andre
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Ian Fette (イアンフェッティ)
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Justin Lee
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Brodie Thiesfield
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Takeshi Yoshino
- Re: [hybi] Clarify the role of closing handshake Gabriel Montenegro
- Re: [hybi] Clarify the role of closing handshake Yutaka_Takeda