[whatwg] canvas, img, file api and blobs
stef at epardaud.fr
Wed Feb 17 00:35:08 PST 2010
On Tue, Feb 16, 2010 at 07:25:34PM +0000, Stefan Haustein wrote:
> We've been getting pretty good traction on Vlad's ArrayBuffers proposal,
> which was taken from the WebGL spec. Our current plan is to change the
> names in the browsers (WebKit, Chrome and Mozilla) to the "non-WebGL
> specific" names Vlad proposes in his spec. We'd really like this to be the
> "one true binary data access" mechanism for HTML. We're talking to the
> File API guys about this and I think this API can be adapted in all the
> other places as well.
> As far as performance goes, can you point me at some quantitative data?
> When you say it's an "orders-of-magnitude" bottleneck, what are you
> comparing it to? The API is very new and we certainly want to improve it
> for the various purposes it can be put to. We've even talked about
> optimizations inside the JS implementations to improve access performance.
If we can get something akin to Java's System.arraycopy (
) then the ArrayBuffer proposal would work for me :)
If we cannot copy ArrayBuffer ranges by blocks in an effecient manner,
then it's going to be very limiting.
More information about the whatwg