4 ms·
While I appreciate SPDY, what's the point of a draft if adoption is so far not widespread? Google's documentation seemed quite sufficient to implement, and unt
by scott_karana 14y ago
While I appreciate SPDY, what's the point of a draft if adoption is so far not widespread?
Google's documentation seemed quite sufficient to implement, and until we have a proper reference implementation, this seems a little half-cocked.
Maybe I misunderstand the point of the IETF draft?
- joshmoz 14y agoFirefox, Chrome, and Opera support SPDY. Apache, nginx, and Node.js support it. Large Google sites support SPDY (gmail), so does Twitter, and Facebook is working on it (http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/0251.html http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/...). I don't know what qualifies as widespread to you, but this is at least a great start. And there are plenty of good implementations to reference.
- Ironlink 14y agoAlso, CloudFlare: http://blog.cloudflare.com/introducing-spdy http://blog.cloudflare.com/introducing-spdy