Jetty and CometD Expert Services
Following the releases of Eclipse Jetty 10.0.0 and 11.0.0, the Reactive HttpClient project — introduced back in 2017 — has released versions 1.1.5, 2.0.0 and 3.0.0. Reactive HttpClient 1.1.x Series Reactive HttpClient Versions 1.1.x, of which the latest is the
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
Starting with patch 9.4.3, Jetty will be fully compliant with RFC6265, which presents changes to cookies which may have significant impact for some users. Up until now Jetty has supported Version=1 cookies defined in RFC2109 (and continued in RFC2965) which allows for special/reserved
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
I was invited to speak at the JAX conference in Mainz about HTTP/2. Jetty has always been a front-runner when it’s about web protocols: first with WebSocket, then with SPDY and finally with HTTP/2. We believe that HTTP/2 is going
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
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.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
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
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,