Page History

...

1. HTTP/2 in Warp with Haskell lightweight threads (by Kazu Yamamoto)
2. Server Implementations of HTTP/2 Priority (by Kazu Yamamoto)
3. Stream scheduling untilizing HTTP/2 priority (by Tatsuhiro Tsujikawa)
4. TLS Performance Report (by Takeru Sasaki)

Discussion Session

1. Refactoring HTTP/2 Component of ATS (by Masaori Koshiba)
   
   • It doesn't make sense to make Http2Stream continuation.
     • Decode HPACK in parallel is an idea.
   • FetchSM & PluginVC
     • It comes from SPDY Plugin, but HTTP/2 is in core now. We should not use FetchSM.
     • It looks difficult to avoid PluginVC.
     • Checking cache via CacheSM in Http2Stream is an idea.
   • It make sense to separate HTTP/2 and HPACK.
   • Current HTTP/2 implementation is 50% slower than HTTPS 
   • Optimize HPACK Decoder
     • Implementation and Analysis of HPACK 05
     • http://www.mew.org/~kazu/material/2014-hpack.pdf (Japanese)
   • Back-postiong
     • nghttpx has intermidate data structure.
   • What we should implement is Stream Priority. Put off Server Push and Back-posting.
     • Benchmarks - H2O 
     • Comparing first-paint of HTTP/1.1, SPDY and HTTP/2 on FireFox (a slide from http://www.slideshare.net/kazuho/http2-51888328 (Japanese))
2. Resource Limitation (by Ryo Okubo)
3. Testing HTTP/2
   • h2spec - A conformance testing tool for HTTP/2 implementation (by Moto Ishizawa)
     • Using gopkg.in to distribute h2spec is proposed
     • Trailing header test passes when we send a RST_STREAM frame is sent
     • Using httpbin to test HTTP/2 gateway server is an idea
   • TSQA, unit test, regression test
4. Free Discussion 
   • Server Push
   • etc
5. Bug scrub : Unresolved HTTP/2 Component Tickets

...