A producer consumer pattern for Jetty HTTP/2 with mechanical sympathy Developing scalable servers in Java now requires careful consideration of mechanical sympathetic issues to achieve both high throughput and low latency. With the introduction of HTTP/2 multiplexed semantics to Jetty,
HTTP/2 Push Demo
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,
Last NPN & ALPN Update for JDK 7
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
HTTP/2 Support for HttpClient
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
Phasing out SPDY support
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
HTTP2 Last Call as Proposed Standard
The HTTP2 protocol has been submitted on the next stage to becoming an internet standard, the last call to the IESG. Some feedback has been highly critical, and has sparked its own lengthy feedback. I have previously given my own
JavaOne 2014 Servlet 3.1 Async I/O Session
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
CometD RemoteCall APIs
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
Jetty 7 and Jetty 8 – End of Life
Five years ago we migrated the Jetty project from The Codehaus to the Eclipse Foundation. In that time we have pushed out 101 releases of Jetty 7 and Jetty 8, double that if you count the artifacts that had to
Jetty @ JavaOne 2014
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