IETF Logo Mail Archive

Re: [hybi] WS framing alternative

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 27 October 2009 11:15 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 464B628C118 for <hybi@core3.amsl.com>; Tue, 27 Oct 2009 04:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.792
X-Spam-Level:
X-Spam-Status: No, score=0.792 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3]
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 mhWzQCaM7TUz for <hybi@core3.amsl.com>; Tue, 27 Oct 2009 04:15:47 -0700 (PDT)
Received: from scmailgw01.scop.aoyama.ac.jp (scmailgw01.scop.aoyama.ac.jp [133.2.251.41]) by core3.amsl.com (Postfix) with ESMTP id 365473A6927 for <hybi@ietf.org>; Tue, 27 Oct 2009 04:15:47 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp (scmse02.scbb.aoyama.ac.jp [133.2.253.159]) by scmailgw01.scop.aoyama.ac.jp (secret/secret) with SMTP id n9RBG0lc028349 for <hybi@ietf.org>; Tue, 27 Oct 2009 20:16:00 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 5fc4_1b6f8ce2_c2ea_11de_8693_001d096c5782; Tue, 27 Oct 2009 20:16:00 +0900
Received: from [IPv6:::1] ([133.2.210.1]:35521) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S12458C1> for <hybi@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 27 Oct 2009 20:12:32 +0900
Message-ID: <4AE6D661.1090007@it.aoyama.ac.jp>
Date: Tue, 27 Oct 2009 20:15:45 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090108 Eudora/3.0b1pre
MIME-Version: 1.0
To: Greg Wilkins <gregw@webtide.com>
References: <8B0A9FCBB9832F43971E38010638454F0F1EA72C@SISPE7MB1.commscope.com> <Pine.LNX.4.62.0910270903080.9145@hixie.dreamhostps.com> <4AE6C6A8.6090307@webtide.com>
In-Reply-To: <4AE6C6A8.6090307@webtide.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "hybi@ietf.org" <hybi@ietf.org>, "Thomson, Martin" <Martin.Thomson@andrew.com>
Subject: Re: [hybi] WS framing alternative
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Tue, 27 Oct 2009 11:15:48 -0000

On 2009/10/27 19:08, Greg Wilkins wrote:

> Existing UTF-8 to character conversions will error if they get a partial
> multipart character,

No, good transcoding libraries have options that say what to do in such 
a case. Iconv is definitely an example, String#encode in Ruby is another.

> so you can start conversion to characters until
> you have the entire message.

I assume you wanted to say "cannot start conversion". False as explained 
above.

> Efficient implementations will be forced
> to reimplement utf-8 converters to scan for 0x00 while converting.

No. These two concerns can be separated completely.

And there's the case that no conversion from utf-8 to characters is 
needed (when your implementation uses utf-8 for its internal 
representation, as e.g. in Perl or (mostly) in Ruby). (Still, you better 
check for consistent UTF-8 byte sequences.)

Regards,   Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

v2.23.0 | Report a Bug | By Email