With the approach of the release candidate for Jetty 9.3.0 in the next days, we have implemented support for HTTP/2 cleartext upgrade mechanism, on server side, resolving issue #465857. This means that you can configure a Jetty server to speak cleartext HTTP/1.1 and cleartext HTTP/2 on the same server port. Read more…
I have recently presented “HTTP/2 and Java: Current Status” at a few conferences (slides below). HTTP/2 and Java: Current Status from Simone Bordet The HTTP/2 protocol has two big benefits over HTTP/1.1: Multiplexing and HTTP/2 Push. The first feature, Multiplexing, gives an edge to modern web sites that perform ~100 Read more…
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 with it, the first pure Java NPN implementation that was Read more…
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…
Greg Wilkins gave the following session at JavaOne 2014 about Servlet 3.1 Async I/O. It’s a great talk in many ways. You get to know from an insider of the Servlet Expert Group about the design of the Servlet 3.1 Async I/O APIs. You get to know from the person Read more…
CometD is a library collection that allows developers to write web messaging applications: you can send messages from servers to client, from clients to servers, from clients to other clients (via servers), and from server to server (using its clustering solution). I wrote about these styles of communications in a 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…
A couple of months ago the CometD Project released its third major version, CometD 3.0.0 (announcement). Since then I wanted to write a blog about this major release, but work on HTTP 2 kept me busy. Today CometD 3.0.1 was released, so it’s time for a new CometD blog entry. 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…