Simone Bordet and I spoke at JavaOne this year about the evolution of web protocol and how HTTP is being replaced by WebSocket (for new semantics) and by SPDY (for better efficiency). The demonstration of SPDY Push is particularly good
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-SPDY blogged
Jos Dirksen has written a nice blog about Jetty-SPDY, thanks Jos ! In the upcoming Jetty 7.6.3 and 8.1.3 (due in the next days), the Jetty-SPDY module has been enhanced with support for prioritized streams and for SPDY push (although
Jetty-SPDY is joining the revolution!
There is a revolution quietly happening on the web and if you blink you might miss it. The revolution is in the speed and latency with which some browsers can load some web pages, and what used to take 100’s
SPDY support in Jetty
SPDY is Google’s protocol that is intended to improve user experience on the web, by reducing the latency of web pages, sometimes up to a factor of 3. Yes, three times faster. How does SPDY accomplish that ? SPDY reduces