Re: [hybi] Additional WebSocket Close Error Codes

"Arman Djusupov" <arman@noemax.com> Thu, 17 May 2012 09:06 UTC

Return-Path: <arman@noemax.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1934921F861F for <hybi@ietfa.amsl.com>; Thu, 17 May 2012 02:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zT8HXO7xaYOV for <hybi@ietfa.amsl.com>; Thu, 17 May 2012 02:06:03 -0700 (PDT)
Received: from mail.noemax.com (mail.noemax.com [64.34.201.8]) by ietfa.amsl.com (Postfix) with ESMTP id 38D2021F861C for <hybi@ietf.org>; Thu, 17 May 2012 02:06:03 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; t=1337245558; x=1337850358; s=m1024; d=noemax.com; c=relaxed/relaxed; v=1; bh=VsWSAiGRCTz+dOvO52+gnesTODk=; h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; b=M0/LHpvZWJSRJuumUyjHMslyhbpTBeL0suZTJVBtkgUQNTU/SjZFVW9/mxXOmjlket5/dG1EIOUVgb/s4ltGCW9Dno1VtFRn37DkL32EzwD8YA8MjXX0bN67euX0DOCOb97Een2tuGQo1Phk0jHXhjOtlTywlkruwaUrYbmPP0w=
Received: from mail.noemax.com by mail.noemax.com (IceWarp 10.4.0) with ASMTP (SSL) id BOW92157; Thu, 17 May 2012 12:05:57 +0300
From: "Arman Djusupov" <arman@noemax.com>
To: "'Alexey Melnikov'" <alexey.melnikov@isode.com>, "'Hybi'" <hybi@ietf.org>
References: <4FB3765D.5060308@isode.com>
In-Reply-To: <4FB3765D.5060308@isode.com>
Date: Thu, 17 May 2012 12:05:48 +0300
Message-ID: <001401cd340c$446034e0$cd209ea0$@noemax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGn5U20RX9qe93aljPngTG1eIMAF5cYTViQ
Content-Language: en-us
Subject: Re: [hybi] Additional WebSocket Close Error Codes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 17 May 2012 09:06:05 -0000

Yes. These status codes do make sense and it is preferable to have them
standardized.

With best regards,
Arman

-----Original Message-----
From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
Alexey Melnikov
Sent: Wednesday, May 16, 2012 12:42 PM
To: Hybi
Subject: [hybi] Additional WebSocket Close Error Codes

Hi WG,
I am sorry I didn't followup on this when the following 2 codes were 
suggested (See 
<http://www.ietf.org/mail-archive/web/hybi/current/msg09284.html>):

1012/Service Restart
1012 indicates that the service is restarted. a client may reconnect, 
and if it choses to do, should reconnect using a randomized delay of 5 - 
30s.

Use case:
restart a service with 100k clients connected
clients present an informative user notification ("service restarting .. 
reconnecting in N secs)
clients should not reconnect all at exactly the same time .. thus the 
randomized delay


1013/Service Overload
1013 indicates that the service is experiencing overload. a client 
should only connect to a different IP (when there are multiple for the 
target) or reconnect to the same IP upon user action.

Use case:
clients present an informative user notification ("service overload .. 
try later or try different IP)

-----

Do people use these and is there still some interest in registering them?

Best Regards,
Alexey

_______________________________________________
hybi mailing list
hybi@ietf.org
https://www.ietf.org/mailman/listinfo/hybi