Re: [hybi] Additional WebSocket Close Error Codes

Greg Wilkins <gregw@intalio.com> Mon, 21 May 2012 10:45 UTC

Return-Path: <gregw@intalio.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 BB40D21F8518 for <hybi@ietfa.amsl.com>; Mon, 21 May 2012 03:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 C5R7vvb33TP7 for <hybi@ietfa.amsl.com>; Mon, 21 May 2012 03:45:05 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id F2C6021F84A2 for <hybi@ietf.org>; Mon, 21 May 2012 03:45:04 -0700 (PDT)
Received: by qabj40 with SMTP id j40so1791047qab.15 for <hybi@ietf.org>; Mon, 21 May 2012 03:45:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=H9O1+5Mcf35kCQLK1Ag1xzXi0u/asD8M0BUeTo08PiY=; b=jtb6T7sd1l8YixMxoeXGghBRAuNDI4P3tcaepiMWjR8xSD0RSL5CWmS+GBsIBur7Il HZCNWYQgYPV+CvT9Oklai7+XPL/Wwe1okGEDMbAt/6pg6bmg6JVYnr/jePZySK18dRmk Dkj9AcXYdfRj9wQQBjQUDxaC4dkK0B5ObF8RdC1O29sx7tfSdGH8WBdFpvra9YaqRInd yr0RzNrHsqaQT0/symKEcQ5Ujakoh9udZl4jiH+DMIl+fcwVlnK16ABqrMrNvjZWWI5C Kb7i/UZ8g5E6ZzrxuXkFyMGXp94qC1NZyASB0p8H7F7zk/5X3d17XvggGlyXpIIyF8Rp 3ewA==
MIME-Version: 1.0
Received: by 10.224.181.84 with SMTP id bx20mr37641495qab.77.1337597104178; Mon, 21 May 2012 03:45:04 -0700 (PDT)
Received: by 10.229.72.97 with HTTP; Mon, 21 May 2012 03:45:04 -0700 (PDT)
In-Reply-To: <001401cd340c$446034e0$cd209ea0$@noemax.com>
References: <4FB3765D.5060308@isode.com> <001401cd340c$446034e0$cd209ea0$@noemax.com>
Date: Mon, 21 May 2012 12:45:04 +0200
Message-ID: <CAH_y2NEqgUKeu5VHYkm59vmybseq6gkMNQqCY0WcqM8BSYtSrQ@mail.gmail.com>
From: Greg Wilkins <gregw@intalio.com>
To: Arman Djusupov <arman@noemax.com>
Content-Type: multipart/alternative; boundary=20cf30334b573f466804c089985b
X-Gm-Message-State: ALoCoQmoJHT4BcLII2iYxPIS7V2Pgg2XAr3f3jDaB7eU6v3GngcDbfFmIEtOpKmVORVxw6aXoUX6
Cc: Hybi <hybi@ietf.org>
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: Mon, 21 May 2012 10:45:05 -0000

They both look reasonable.

On 17 May 2012 11:05, Arman Djusupov <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] 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
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>