What would #aleph like to see from HTTP/2? Improved performance? Want to prioritize different requests/streams/assets? Want flow control? Something else? I'd like to hear any and all expectations and desires!
(From my point of view as an Aleph user)
What I would expect from Aleph is the improved performance provided by HTTP/2 out-of-the-box while still being ring-compliant. I don't have any use cases where I would like to do streams prioritization.
While we are stuck with HTTP/1.1 for compliance, an important feature Aleph provides is the raw-stream? parameter to perform asynchronous pipelines and avoid copying objects on the heap (DirectByteBuf).
I would expect to sill have access to this when HTTP/2 will be supported. Either as stream of ByteBuf or Http2Frame.