Re: [hybi] Additional WebSocket Close Error Codes
Alexey Melnikov <alexey.melnikov@isode.com> Thu, 24 May 2012 12:52 UTC
Return-Path: <alexey.melnikov@isode.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 339CC21F85D1 for <hybi@ietfa.amsl.com>; Thu, 24 May 2012 05:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.311
X-Spam-Level:
X-Spam-Status: No, score=-102.311 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 0Pqu+QaR6IjQ for <hybi@ietfa.amsl.com>; Thu, 24 May 2012 05:52:25 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id E4B5D21F8512 for <hybi@ietf.org>; Thu, 24 May 2012 05:52:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1337863944; d=isode.com; s=selector; i=@isode.com; bh=rf35vjdSAQr1ccbOnHT/MK89X3K8lKUDJoSHRLd5rFg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=wQlTowbE3q4TsGMugTWfgv7tKKEqDWEyD1xbNWxSw+LdfZDVqe92v+qSRIw/bJK5JhqM1R 7jGeS28TzitvL9n7VC8RbpQBrKmJwA6LiCitXcwCIVLlTKBxTZ3bfWH3rBPKavUDfLEth5 PmhU2/b9UHDN0tr+EDCtW3OMBrqmym4=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T74vCAAE4xCA@rufus.isode.com>; Thu, 24 May 2012 13:52:24 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FBE2F1E.1030307@isode.com>
Date: Thu, 24 May 2012 13:52:46 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Hybi <hybi@ietf.org>
References: <4FB3765D.5060308@isode.com> <001401cd340c$446034e0$cd209ea0$@noemax.com> <CAH_y2NEqgUKeu5VHYkm59vmybseq6gkMNQqCY0WcqM8BSYtSrQ@mail.gmail.com>
In-Reply-To: <CAH_y2NEqgUKeu5VHYkm59vmybseq6gkMNQqCY0WcqM8BSYtSrQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------060206050902070401060506"
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, 24 May 2012 12:52:26 -0000
On 21/05/2012 11:45, Greg Wilkins wrote: > > They both look reasonable. Ok, I will register these, but I will call the second one "Try Again Later" instead of "Service Overload". "Try Again Later" is used by other protocols and the meaning is more generic. > On 17 May 2012 11:05, Arman Djusupov <arman@noemax.com > <mailto:arman@noemax.com>> wrote: > > 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> > [mailto: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 <mailto:hybi@ietf.org> > https://www.ietf.org/mailman/listinfo/hybi > > _______________________________________________ > hybi mailing list > hybi@ietf.org <mailto:hybi@ietf.org> > https://www.ietf.org/mailman/listinfo/hybi > >
- [hybi] Additional WebSocket Close Error Codes Alexey Melnikov
- Re: [hybi] Additional WebSocket Close Error Codes Arman Djusupov
- Re: [hybi] Additional WebSocket Close Error Codes Greg Wilkins
- Re: [hybi] Additional WebSocket Close Error Codes Alexey Melnikov
- Re: [hybi] Additional WebSocket Close Error Codes Jason Duell
- Re: [hybi] Additional WebSocket Close Error Codes Salvatore Loreto
- Re: [hybi] Additional WebSocket Close Error Codes Alexey Melnikov
- Re: [hybi] Additional WebSocket Close Error Codes Jason Duell
- Re: [hybi] Additional WebSocket Close Error Codes Jamie Lokier
- Re: [hybi] Additional WebSocket Close Error Codes Tobias Oberstein