Re: [hybi] thewebsocketprotocol #40 (closed): Clarify binary/utf-8 mixed handling
"hybi issue tracker" <trac@tools.ietf.org> Mon, 21 February 2011 11:20 UTC
Return-Path: <trac@tools.ietf.org>
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 B6A9E3A70D2 for <hybi@core3.amsl.com>; Mon, 21 Feb 2011 03:20:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
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 ueU6577Rp-MY for <hybi@core3.amsl.com>; Mon, 21 Feb 2011 03:20:10 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id DE00C3A70CE for <hybi@ietf.org>; Mon, 21 Feb 2011 03:20:10 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1PrTov-000596-DE; Mon, 21 Feb 2011 03:20:49 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: hybi issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: jat@google.com, salvatore.loreto@ericsson.com
X-Trac-Project: hybi
Date: Mon, 21 Feb 2011 11:20:49 -0000
X-URL: http://tools.ietf.org/hybi/
X-Trac-Ticket-URL: https://wiki.tools.ietf.org/wg/hybi/trac/ticket/40#comment:2
Message-ID: <072.d163836b8d9574eb472fe38817256fc9@tools.ietf.org>
References: <063.e489b6d352cc1192d00acf7f96150ea7@tools.ietf.org>
X-Trac-Ticket-ID: 40
In-Reply-To: <063.e489b6d352cc1192d00acf7f96150ea7@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: jat@google.com, salvatore.loreto@ericsson.com, hybi@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: hybi@ietf.org
Subject: Re: [hybi] thewebsocketprotocol #40 (closed): Clarify binary/utf-8 mixed handling
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
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: Mon, 21 Feb 2011 11:20:12 -0000
#40: Clarify binary/utf-8 mixed handling Changes (by salvatore.loreto@…): * status: new => closed * resolution: => invalid Old description: > It can be confusing to mix binary and utf-8 frames in one tcp-like > stream. For example, what will the current text-only JS Websocket API do > if suddenly binary starts appearing? > Additionally, when only partial frames may be available, it is expensive > to verify that this is indeed a valid UTF-8 stream (protocol > implementation needs to take into account multi-byte characters and end > of current data payload). If binary has been negotiated for this > session, processing can be optimized accordingly. > > Proposal: allow negotiation to clarify if a stream will not mix binary > and text in order to enable optimizing for the binary-only case. New description: It can be confusing to mix binary and utf-8 frames in one tcp-like stream. For example, what will the current text-only JS Websocket API do if suddenly binary starts appearing? Additionally, when only partial frames may be available, it is expensive to verify that this is indeed a valid UTF-8 stream (protocol implementation needs to take into account multi-byte characters and end of current data payload). If binary has been negotiated for this session, processing can be optimized accordingly. Proposal: allow negotiation to clarify if a stream will not mix binary and text in order to enable optimizing for the binary-only case. -- Comment: closed... some clarification text will be added in 06 see: http://www.ietf.org/mail-archive/web/hybi/current/msg06311.html -- --------------------------------------+------------------------------------- Reporter: g_e_montenegro@… | Owner: Type: defect | Status: closed Priority: major | Milestone: Component: thewebsocketprotocol | Version: Severity: - | Resolution: invalid Keywords: | --------------------------------------+------------------------------------- Ticket URL: <https://wiki.tools.ietf.org/wg/hybi/trac/ticket/40#comment:2> hybi <http://tools.ietf.org/hybi/> The Hypertext-Bidirectional (HyBi) working group will seek standardization of one approach to maintain bidirectional communications between the HTTP client, server and intermediate entities, which will provide more efficiency compared to the current use of hanging requests.
- [hybi] thewebsocketprotocol #40 (new): Clarify bi… hybi issue tracker
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… hybi issue tracker
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… Bjoern Hoehrmann
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… Gabriel Montenegro
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… Bjoern Hoehrmann
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… John Tamplin
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… Gabriel Montenegro
- Re: [hybi] thewebsocketprotocol #40 (new): Clarif… John Tamplin
- Re: [hybi] thewebsocketprotocol #40 (closed): Cla… hybi issue tracker