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.
I posted a while back about the capability of Jetty 9.1’s HttpClient to speak HTTP over different transports: by default HTTP, but we also provide a SPDY implementation, where the HTTP requests and responses are carried using the SPDY transport
In Jetty 9, the HttpClient was completely rewritten, as we posted a while back. In Jetty 9.1, we took one step forward and we made Jetty’s HttpClient polyglot. This means that now applications can use the HTTP API and semantic
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
We have SPDY to SPDY and HTTP to SPDY proxy functionality implemented in Jetty for a while now. An important and very common use case however is a SPDY to HTTP proxy. Imagine a network architecture where network components like
Having discussed the business case for Jetty 9 and SPDY, this blog presents a simple tutorial for runing PHP web applications like WordPress on Jetty with SPDY. Get Jetty First you’ll need a distribution of Jetty, which you can download,
So you are not Google! Your website is only taking a few 10’s or maybe 100’s of requests a second and your current server is handling it without a blip. So you think you don’t need a faster server and
Jetty 9.1.0 has entered round 8 of the Techempower’s Web Framework Benchmarks. These benchmarks are a comparison of over 80 framework & server stacks in a variety of load tests. I’m the first one to complain about unrealistic benchmarks when
Introduction One of the big refactorings in Jetty 9 is the complete rewrite of the HTTP client. The reasons behind the rewrite are many: We wrote the codebase several years ago; while we have actively maintained, it was starting to
The SPDY protocol will be the next web revolution. The HTTP-bis working group has been rechartered to use SPDY as the basis for HTTP 2.0, so network and server vendors are starting to update their offerings to include SPDY support.