- From: 張俊芝 <notifications@github.com>
- Date: Sat, 07 Dec 2019 02:08:00 -0800
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 7 December 2019 10:08:39 UTC
> I understand, I was basically asking if the writing would be done similarly to https://encoding.spec.whatwg.org/#dom-textencoder-encodeinto. So unless you're multi-threaded and use `SharedArrayBuffer`, you cannot observe a partially filled buffer. Did you mean that I can use `SharedArrayBuffer` together with `encodeInto` via multi-threads, so WASM can work early whiling stilling coping buffer to WASM memory, as a workaround to reduce latency? But consider if I am reading **a 100MB file which is not of streaming format**, that means unless the whold 100MB content of the file has been ready in WSAM memory, partically ready content doesn't have much value. In that case, `SharedArrayBuffer` + `encodeInto` still doesn't help much. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/FileAPI/issues/143#issuecomment-562836379
Received on Saturday, 7 December 2019 10:08:39 UTC