W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [FileAPI] Remove readAsBinaryString?

From: Charles Pritchard <chuck@jumis.com>
Date: Fri, 16 Dec 2011 02:12:21 -0800
Message-Id: <5684F14D-F702-4DB8-AC5B-5AA3E043D34D@jumis.com>
Cc: Adrian Bateman <adrianba@microsoft.com>, Feras Moussa <ferasm@microsoft.com>, "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
To: Arun Ranganathan <aranganathan@mozilla.com>
Wouldn't mind a more managed log of API shifts. Any ideas for a very simple deprecation journal?

I just learned about CanvasPixelArray being turned over today and I follow the lists.

A simple HTML.deprecated list would have the dual use of notifying followers about strong progress. It'd relieve editors of some of these concerns.

Anyway, hopeful thought.

On topic: anyone using readAsBinaryString ought to be testing for Typed Arrays first. Take it out of the spec. Consider placing it somewhere else for those times when a quick web search helps.


On Dec 16, 2011, at 12:42 AM, Arun Ranganathan <aranganathan@mozilla.com> wrote:

> I'm happy to remove this from the specification.  Right now this is marked as deprecated, which I suppose isn't strong enough discouragement?  :)
> ----- Original Message -----
>> Another topic that came up at TPAC was readAsBinaryString [1]. This
>> method
>> predates support for typed arrays in the FileAPI and allows binary
>> data
>> to be read and stored in a string. This is an inefficient way to store
>> data now that we have ArrayBuffer and we'd like to not support this
>> method.
>> At TPAC I proposed that we remove readAsBinaryString from the spec and
>> there was some support for this idea. I'd like to propose that we
>> change
>> the spec to remove this.
>> Thanks,
>> Adrian.
>> [1] http://dev.w3.org/2006/webapi/FileAPI/#readAsBinaryString
Received on Friday, 16 December 2011 10:12:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:37 UTC