- From: Ellem Laboratories <notifications@github.com>
- Date: Mon, 06 Jan 2020 07:51:47 -0800
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 January 2020 15:51:51 UTC
To express my opinion, I think defining a maximum of 0x10000 bytes would be an extremely acceptable idea, and certainly future proof. For comparison, the max size of a UDP packet is around that size as well (0x10000-1 to be exact), and no one has complained about it [since its definition in 1980](https://tools.ietf.org/html/rfc768). However, keep in mind, for my particular application, I would only need a *maximum* defined. As that maximum alone would allow me to optimize heap allocation. Another solution outside of defining a maximum for implementations would be to allow developers like me to pass an argument that would define the maximum in run-time... but at that point, we'd be redefining the BYOB implementation. -- 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#issuecomment-571192244
Received on Monday, 6 January 2020 15:51:51 UTC