Hi, just one little update:
http://stackoverflow.com/questions/37211883/jetty-respond-with-status-200-instead-of-304-while-using-http2 Currently there is a small issue left in which jetty respond with 200 instead of 304 after the second request, even if the server sends the correct PUSH_PROMISE. Hope Jetty devs help me out, soon. :-) kind regards Tobias > Am 12.05.2016 um 18:15 schrieb Maxim Solodovnik <[email protected]>: > > Cool! > > On Thu, May 12, 2016 at 10:10 PM, Tobias Soloschenko < > [email protected]> wrote: > >> Hi, >> >> I just managed to finish a PoC in which Apache Wicket runs on Jetty with >> http/2 and uses the Servlet 4.0 Spec / PushBuilder to provide resources to >> the client. >> >> Notes: >> * Small API which can be added to increase the performance of the webapp >> with http/2 >> * No html changes required >> >> References: >> * >> >> https://raw.githubusercontent.com/klopfdreh/jetty-http2-example/master/without_push.png >> * >> >> https://raw.githubusercontent.com/klopfdreh/jetty-http2-example/master/with_push.png >> >> On localhost improved performance: 37ms latency without and 1ms latency to >> serve the resource (CSS file) >> >> Example Implementation: >> * >> >> https://github.com/klopfdreh/jetty-http2-example/blob/master/de.jetty.wicket.http2.example/src/main/java/de/jetty/wicket/http2/example/HTTP2Page.java#L28 >> >> Jetty Setup: >> * >> >> https://github.com/klopfdreh/jetty-http2-example/blob/master/de.jetty.wicket.http2.example/src/test/java/de/jetty/wicket/http2/example/Runner.java >> >> hooray! >> >> WDYT >> >> kind regards >> >> Tobias > > > > -- > WBR > Maxim aka solomax
