Hacker News new | ask | show | jobs
by amelius 4029 days ago
From [1]:

> when transferring an ArrayBuffer from your main app to Worker, the original ArrayBuffer is cleared and no longer usable

This is really too restrictive in many situations.

[1] https://developers.google.com/web/updates/2011/12/Transferab...

1 comments

That may be what the API requires, but is it actually implemented as a physical move/copy of memory? It sounds like they can just make the array _appear_ to be cleared, while keeping it in place in memory.
The way I understand it is that they usually just move the pointer to the ArrayBuffer's underlying data store. No block copy occurs.