Jetty and CometD Expert Services
Jetty 9 introduced the Eat-What-You-Kill execution strategy to apply mechanically sympathetic techniques to the scheduling of threads in the producer-consumer pattern that are used for core capabilities in the server. The initial implementations proved vulnerable to thread starvation and Jetty-9.3 introduced dual
Jetty’s venerable MultiPartInputStreamParser for parsing MultiPart form-data has been deprecated and replaced by the much more efficient MultiPartFormInputStream, based on a new MultiPartParser. This is much faster, but less forgiving of non-compliant format. So we have implemented a legacy mode
This is going to be a blog of mixed metaphors as I try to explain how we avoid thread starvation when we use Jetty’s eat-what-you-kill scheduling strategy. Jetty has several instances of a computing pattern called ProduceConsume, where a task
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
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
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,
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,
The auto discovery features of the Servlet specification can make deployments slow and uncertain. Working in collaboration with Google AppEngine, the Jetty team has developed the Jetty quick start mechanism that allows rapid and consistent starting of a Servlet server.
While Jetty has internally used asynchronous IO since 7.0, Servlet 3.1 has added asynchronous IO to the application API and Jetty-9.1 now supports asynchronous IO in an unbroken chain from application to socket. Asynchronous APIs can often look intuitively simple,
After having some discussions on spdy-dev and having some experience with our current push implementation, we’ve decided to change a few things to the better. Jetty now sends all push resources non interleaved to the client. That means that the