W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: ByteString in Web IDL

From: Robin Berjon <robin@w3.org>
Date: Thu, 11 Jul 2013 10:25:21 +0200
Message-ID: <51DE6BF1.3050003@w3.org>
To: Anne van Kesteren <annevk@annevk.nl>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
On 10/07/2013 16:04 , Anne van Kesteren wrote:
> On Wed, Jul 10, 2013 at 9:39 AM, Robin Berjon <robin@w3.org> wrote:
>> It's just a name, nothing keeps you from using it if you know what you're
>> doing — it's just about scaring off people who don't. Besides, you might
>> need ByteStrings in a new API, but only if you're interfacing with some form
>> of legacy content.
>
> I don't understand. HTTP is and will remain bytes, but in the
> confusing way that the bytes look like strings. Any new API around
> that would not be legacy

But HTTP is.

End of bikeshed, it was just a suggestion.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 11 July 2013 08:25:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC