Re: [hybi] Additional WebSocket Close Error Codes

"Arman Djusupov" <> Thu, 17 May 2012 09:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1934921F861F for <>; Thu, 17 May 2012 02:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zT8HXO7xaYOV for <>; Thu, 17 May 2012 02:06:03 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 38D2021F861C for <>; Thu, 17 May 2012 02:06:03 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; t=1337245558; x=1337850358; s=m1024;; 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 by (IceWarp 10.4.0) with ASMTP (SSL) id BOW92157; Thu, 17 May 2012 12:05:57 +0300
From: Arman Djusupov <>
To: 'Alexey Melnikov' <>, 'Hybi' <>
References: <>
In-Reply-To: <>
Date: Thu, 17 May 2012 12:05:48 +0300
Message-ID: <001401cd340c$446034e0$cd209ea0$>
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-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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

With best regards,

-----Original Message-----
From: [] 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 

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 - 

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,

hybi mailing list