Re: [hybi] Clarify the role of closing handshake

Yutaka_Takeda@PlayStation.Sony.Com Tue, 15 February 2011 21:45 UTC

Return-Path: <Yutaka_Takeda@PlayStation.Sony.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 958003A6AFD; Tue, 15 Feb 2011 13:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.945
X-Spam-Level:
X-Spam-Status: No, score=-5.945 tagged_above=-999 required=5 tests=[AWL=0.319, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 ylGBzNPUpd8N; Tue, 15 Feb 2011 13:45:03 -0800 (PST)
Received: from paris.playstation.sony.com (nat.playstation.sony.com [69.36.131.254]) by core3.amsl.com (Postfix) with ESMTP id 14F773A6ADB; Tue, 15 Feb 2011 13:45:01 -0800 (PST)
Received: from constantine.playstation.sony.com ([162.49.67.15]) by paris.playstation.sony.com (Lotus Domino Release 8.5.1FP5) with ESMTP id 2011021513452108-577167 ; Tue, 15 Feb 2011 13:45:21 -0800
In-Reply-To: <4D5AE318.9080308@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
MIME-Version: 1.0
X-KeepSent: 9E69202E:36384265-88257838:00749E83; type=4; flags=0; name=$KeepSent
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF9E69202E.36384265-ON88257838.00749E83-88257838.007782CA@playstation.sony.com>
From: Yutaka_Takeda@PlayStation.Sony.Com
Date: Tue, 15 Feb 2011 13:45:22 -0800
X-MIMETrack: Serialize by Router on SCEA919ML04/SCEA(Release 8.5.1FP3|May 23, 2010) at 02/15/2011 01:45:20 PM, Serialize complete at 02/15/2011 01:45:20 PM, Itemize by SMTP Server on SCEA919ML02/SCEA(Release 8.5.1FP5|September 29, 2010) at 02/15/2011 01:45:21 PM, Serialize by Router on SCEA919ML02/SCEA(Release 8.5.1FP5|September 29, 2010) at 02/15/2011 01:45:28 PM, Serialize complete at 02/15/2011 01:45:28 PM
Content-Type: multipart/alternative; boundary="=_alternative 007782C988257838_="
Cc: hybi-bounces@ietf.org, hybi@ietf.org
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 21:45:05 -0000

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)

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?

# trying to figure out whether graceful shutdown at least during 'closing' 
state would ever be helpful.

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