Re: [streams] Maybe giving async readInto (and read?) another shot (#290)

@piscisaureus I doubt there is a way to parse TLS properly and securely without actually buffering the contents of the incoming TCP packets. If you are going to read into such buffer - double-allocations and memory copying would be wasteful and will destroy performance (as it did in node.js 0.10 TLS implementation).

To conclude: there is nothing OpenSSL-specific, or hacky in the way we use `.readInto()` (under other name, though) in io.js. It is perfectly normal to assume that this method would be performance critical for the protocol implementations, where buffering is inevitable.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/290#issuecomment-76500577