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
Jetty SPDY to HTTP Proxy
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
Why detecting concurrent issues can be difficult
Jetty 9’s NIO code is a nearly complete rewrite with improved architecture, cleaner and clearer code base and best of all it’ll be even faster and more efficient than jetty 7/8’s NIO layer. Detecting concurrent code issues is usually not
Fully functional SPDY-Proxy
We keep pushing our SPDY implementation and with the upcoming Jetty release we provide a fully functional SPDY proxy server out of the box. Simply by configuration you can setup Jetty to provide a SPDY connector where clients can connect
SPDY – non representative benchmark for plain http vs. spdy+push on webtide.com
I’ve done a quick run with the Page Benchmarker Extension on chromium to measure the difference between http and SPDY + push. Enabling benchmarks restricts chromium to SPDY draft 2 so we’ll run without flow control. Note that the website
SPDY – we push!
SPDY, Google’s web protocol, is gaining momentum. Intending to improve the user’s web experience it aims at severely reducing page load times. We’ve blogged about the protocol and jetty’s straight forward SPDY support already: Jetty-SPDY is joining the revolution! and
Jetty JMX Webservice
Jetty JMX Webservice is a webapp providing a RESTful API to query JMX mbeans and invoke mbean operations without the hassle that comes with RMI. No more arguments with your firewall admin, just a single http port. That alone might