Here’s an example:
const buffer = new ArrayBuffer(64) const view = new DataView(buffer)
Since this is a view over a buffer, we can specify which byte we want to start from, and the length:
const view = new DataView(buffer, 10) //start at byte 10
const view = new DataView(buffer, 10, 30) //start at byte 10, and add 30 items
If we don’t add those additional arguments, the view starts at position 0 and loads all the bytes present in the buffer.
There is a set of methods we can use to add data into the buffer:
This is how to call one of those methods:
const buffer = new ArrayBuffer(64) const view = new DataView(buffer) view.setInt16(0, 2019)
By default data is stored using big endian notation. You can overwrite this setting and use little endian by adding a third parameter with the
const buffer = new ArrayBuffer(64) const view = new DataView(buffer) view.setInt16(0, 2019, true)
Here is how we can get data from the view:
const buffer = new ArrayBuffer(64) const view = new DataView(buffer) view.setInt16(0, 2019) view.getInt16(0) //2019
DataView is an
ArrayBufferView, we have those 3 read-only properties:
bufferpoints to the original ArrayBuffer
byteOffsetis the offset on that buffer
byteLengthis the length of its content in bytes
One thing to keep in mind is that typed arrays don’t let us control the endianness: it uses the endianness of the system. In general this works out fine, because the main use case as we said is to use the array locally, using one of the multimedia APIs.
If you transfer the data of a Typed Array on another system, the data might be not badly encoded if it uses Big Endian and you use Little Endian.
In case you need this kind of control, DataView is a perfect choice.
Here's my latest YouTube video. I talk about work/life balance as a developer: