hyper
hyper copied to clipboard
HTTP/2 for Python.
This is not something `httplib` supports, so we have nowhere to take our lead from. This means we can do this right (or at least right-ish). So what's our idealised...
[Using this](https://github.com/devsisters/libquic). See also [here](https://groups.google.com/a/chromium.org/forum/#!topic/proto-quic/MIogHT8wacA).
Setting ourselves to a really restricted cipher list as mandated by the specification breaks on Ubuntu 12.04 because Ubuntu are fucking terrible. I've spent all of yesterday trying to fix...
Right now `hyper` doesn't read frames until the user attempts to read data or our connection window closes. This is obviously a problem: 1. We will send all the data...
One way `nginx` achieves great performance when serving static files over HTTP/1.1 is by using the Unix `sendfile` API, which essentially writes data from one FD to another in kernel...
`hyper` is not optimised for performance right now. While the HTTP/2 spec is changing I want to focus on correctness and the ability to easily change behaviour. However, when it...
HTTP/2 currently has a provision for opportunistically encrypting HTTP/2 on port 80. It'd be nice if we could do that too.
Alt-Svc is another way of discovering HTTP/2 support. Again, we'll need a HTTP/1.1 stack for this.
The integration tests are great, but they get really long and rely on a ton of implementation details, which is a bit lame. We should be able to abstract this...
Right now we increment the remote window size when frames are read off the wire, not when they're actually consumed. This can lead to `hyper` growing massive in memory when...