[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Typed Array spec updates: strawman proposals

Love it!

Two comments:

Any reason that it's 'copyRange' instead of 'slice'? 'copyRange' is more explicit, but 'slice' is more consistent.

'isReadOnly' should probably be 'readOnly' (the name that is used elsewhere in the html spec, for example on the <input> element).

Ben Vanik

On Fri, Apr 22, 2011 at 6:20 PM, Kenneth Russell <kbr@google.com> wrote:

The Typed Array editors' draft has been updated:


with changes supporting the following functionality:

 - Ability to copy sections of an ArrayBuffer
 - Read-only ArrayBuffers
 - Support for zero-copy data transfer via postMessage by defining the
behavior of ArrayBuffers and ArrayBufferViews under structured clone

The changes are clearly highlighted in the spec with "Strawman proposal".

The strawman proposal for the behavior of ArrayBuffers and views under
structured clone was discussed informally between Mozilla and Google,
and has undergone some iteration. (Earlier iterations involved making
an explicit API call to achieve transfer of ownership, and having the
default behavior perform a copy.) The current behavior was preferred
by members of the TC-39 committee, because it achieves unsurprising
performance characteristics.

We believe that these changes will be efficiently implementable in
current _javascript_ engines and web browsers.

Your feedback on these changes would be greatly appreciated. Please
send them to the list.


You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl