As you may know already, Oracle has announced that OpenJDK 7, with its last 7u80 release, has reached end of life as of today. In March 2012, the Jetty project announced that it had implemented the SPDY protocol and, along
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
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
I’ll be attending JavaOne Sept 29 to Oct 1 and will be presenting several talks on Jetty: CON2236 Servlet Async IO: I’ll be looking at the servlet 3.1 asynchronous IO API and how to use it for scale and low
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.
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
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
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