IMHO, SPDY should be implemented on the frontend servers like varnish, HAProxy or nginx. If you do SPDY on the backend server, you cause a lot of additional problems:<p>1) your backend servers should use their hardware for actually running the web application, not for encrypting responses.<p>2) usually, your backend servers only serve the dynamically generated content. SPDY's biggest advantage is that it would allow to handle multiple requests in one connection, but this really shines for static assets (images, stylesheets) which in turn are rarely served by the backend.<p>3) Even if you want to do SPDY on the backend, your frontend proxies still have to support it, because that's what the clients are talking to.<p>So as it stands now, having SPDY on the backend server (or even in your application like this project here) doesn't really give you any of SPDY's advantages unless you begin serving all of your site directly from your application servers, which we learned over the last years, just doesn't scale as well.