- From: Ellem Laboratories <notifications@github.com>
- Date: Thu, 02 Jan 2020 18:02:40 -0800
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 3 January 2020 02:02:42 UTC
Currently regarded as 'Issue 1' I have recently come across a project that forces me to assume the chunk size for the stream. Testing with chromium and firefox, the chunk size appears to be `0x10000` or `65536`. I cannot find a reason why it's this particular number. As I'm making a wasm module, I must allocate memory space when going through files 5GB+ in size. I will allocate `0x10000` bytes for now, but only out of assumption... if there's a browser out there that does not follow this assumption then there will be fatal bugs. I'm not sure if this is w3c/FileAPI/'s or streams.spec.whatwg.org's jurisdiction. But neither of them has an exact number. -- 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/144
Received on Friday, 3 January 2020 02:02:42 UTC