[Bug 17263] Keep on having send(ArrayBuffer data) interface in addition to send(ArrayBufferView data)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17263

--- Comment #2 from Takashi Toyoshima <toyoshim@chromium.org> 2012-05-31 12:41:13 UTC ---
If I understand correctly, a browser is not expected to convert ArrayBufferView
to a binary frame in the network byte order or to transform into some platform
independent structure. So there is no difference between ArrayBuffer and
ArrayBufferView from the viewpoint of endian. I think major benefits to use
ArrayBufferView is that we can send a part of ArrayBuffer without any extra
copy. It is because subarray() can create a object which refer a part of the
buffer with start and end offset information.

I could not find authoritative information how TypedArray handle endian. At
least, DataView has interfaces which required explicit endian indication and
its default behavior is big endian. But, in my environment TypedArray works as
little endian. I guess TypedArray depends on platform endian type, but it's
good for use cases of TypedArray.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 31 May 2012 12:41:21 UTC