Jetty’s HttpClient is a fast, scalable, asynchronous implementation of a HTTP client. But it is even more. Jetty’s HttpClient provides a high level API with HTTP semantic. This means that your applications will be able to perform HTTP requests and receive HTTP responses with a rich API. For example, you Read more…
Now that the HTTP/2 specification is in its final phases of approval, big players announced that they will remove support for SPDY in favor of long term support of HTTP/2 (Chromium blog). We expect others to follow soon. Based on this trend and feedback from users the Jetty Project is Read more…
As promised on my last post on HTTP/2, we have implemented and deployed the HTTP/2 Push functionality on this very website, webtide.com. For the other HTTP/2 implementers out there, if you request “/” on webtide.com, you will get “/wp-includes/js/jquery/jquery.js” pushed. We have already implemented SPDY Push in the past, but Read more…
Following my previous post, several players tried their HTTP/2 implementation of draft 14 (h2-14) against webtide.com. A few issues were found and quickly fixed on our side, and this is very good for interoperability. Having worked many times at implementing specifications, I know that different people interpret the same specification Read more…
The IETF HTTP working group has issued a last call for comments on the proposed HTTP/2 standard, which means that the process has entered the final stage of open community review before the current draft may become an RFC. Jetty has implemented the proposal already and this website is running Read more…
Greg Wilkins (@gregwilkins) and I (@simonebordet) have been working on implementing HTTP/2 draft 14 (h2-14), which is the draft that will probably undergo the “last call” at the IETF. We will blog very soon with our opinions about HTTP/2 (stay tuned, it’ll be interesting!), but for the time being Jetty Read more…