In our previous blog, we presented the case of a Webtide customer, Genesys, that needed to integrate CometD in NodeJS and how we developed a CometD client capable of running in the NodeJS environment. In this article we present the other
CometD and NodeJS, part 1
In addition to our Lifecycle Support offerings, Webtide is also committed to helping develop new functionality to meet customer needs for the open source projects Webtide supports, CometD and Eclipse Jetty. Recently Genesys, a global leader in customer experience solutions
HTTP Trailers in Jetty
HTTP/1.1 and HTTP/2 have the concept of trailers, that is HTTP headers that can be sent after the message body, in both requests and responses. In HTTP/1.1 trailers can be sent using the chunked transfer coding, for example in requests
Jetty, Cookies and RFC6265 Compliance
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
Patch for a Patch!
Are you an Eclipse Jetty user who enjoys contributing to the open source project and wants to let the rest of the world know? Of course you are! As a thank you to our great community, we’ve had some fancy
CometD 3.1.0 Released
The CometD Project is happy to announce the availability of CometD 3.1.0. CometD 3.1.0 builds on top of the CometD 3.0.x series, bringing improvements and new features. You can find a migration guide at the official CometD documentation site. What’s
Thread Starvation with Eat What You Kill
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-killThe EatWhatYouKill strategy is named after a hunting proverb in the sense that one should only
HTTP/2 at JAX
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
Unix Sockets for Jetty 9.4?
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!