In the 20th year of Jetty development we are finally considering a bit of native code integration to provide Unix Domain Sockets in Jetty 9.4! Typically the IO performance of pure java has been close enough to native code for
HTTP/2 on Google Compute Engine with Jetty
Now that HTTP/2 is a published standard (RFC 7540) and Jetty-9.3.0 has been released with HTTP/2.0, It’s time to start running this new protocol in your deployments. So let’s look at how you can run HTTP/2 on Google Compute Engine!
HTTP/2 with HAProxy and Jetty
HTTP/2 is now the official RFC 7540, and it’s about time to deploy your website on HTTP/2, to get the numerous benefits that HTTP/2 brings. A very typical deployment is to have Apache (or Nginx) working as a reverse proxy
Introduction to HTTP2 in Jetty
Jetty 9.3 supports HTTP/2 as defined by RFC7540 and it is extremely simple to enable and get started using this new protocol that is available in most current browsers. Getting started with Jetty 9.3 Before we can run HTTP/2, we
Jetty-9.3 Features!
Jetty 9.3.0 is almost ready and Release Candidate 1 is available for download and testing! So this is just a quick blog to introduce you to what is new and encourage you to try it out! HTTP2 The headline feature
Simple Jetty HelloWorld Webapp
With the jetty-maven-plugin and Servlet Annotations, it has never been simpler to start developing with Jetty! While we have not quiet achieved the terseness of some convention over configuration environments/frameworks/languages, it is getting close and only 2 files are needed
G1 Garbage Collector at GeeCON 2015
I had the pleasure to speak at the GeeCON 2015 Conference in Kraków, Poland, where I presented a HTTP/2 session and a new session about the G1 garbage collector (slides below). G1 Garbage Collector: Details and Tuning from Simone Bordet
Jetty HTTP/2 cleartext upgrade
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
Eat What You Kill
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,