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

Re: [FileAPI] Remove readAsBinaryString?

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 13 Dec 2011 17:14:26 -0800
Message-Id: <564D1F9D-DA77-45E2-8564-9A0C099322F0@jumis.com>
Cc: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, Feras Moussa <ferasm@microsoft.com>
To: Adrian Bateman <adrianba@microsoft.com>
Seems quite reasonable to me. We've got data URL strings for people who need inefficiency (or portable strings).



On Dec 13, 2011, at 4:52 PM, Adrian Bateman <adrianba@microsoft.com> wrote:

> 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 Wednesday, 14 December 2011 01:21:44 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT