- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 10 Jul 2013 10:04:37 -0400
- To: Robin Berjon <robin@w3.org>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, Norbert Lindenberg <ecmascript@lindenbergsoftware.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
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 and would have to deal with this somehow. -- http://annevankesteren.nl/
Received on Wednesday, 10 July 2013 14:05:07 UTC