6 ms·
SPDY: What I Like About You
- TamDenholm 15y agoFor those, like me, that didnt know what SPDY was. http://en.wikipedia.org/wiki/SPDY http://en.wikipedia.org/wiki/SPDY
- ck2 15y agoI look forward to SPDY support in Firefox. Now web server software needs to keep up. It took me (years?) to upgrade from Firefox 3.x to 6, but then only a week to upgrade to 7. 6 to 7 was seamless and added handy features - so I am changing my mind on the rapid release schedule as long as extensions aren't broken (often). (7 is in release candidate build 2 already, give it a shot - it feels insanely fast)
- FlowerPower 15y ago"It took me (years?) to upgrade from Firefox 3.x to 6, but then only a week to upgrade to 7." It's just numbers, they dont mean much.
- ck2 15y agoYeah but they used to mean something which is hard to unlearn. Now I just mentally shift them to the right so they are minor version numbers in my head: ie. 1.6 1.7 1.8 etc. and then I can deal with it. But 3.x to 6 is a big jump. Took me an entire weekend of fiddling, tweaking and lots of googling and research to replace extensions and get everything just right.
- drivebyacct2 15y agoYeah, I wish the numbers didn't matter. I love that Chrome auto updates and I never see an extension update dialog box pop up. I love that I don't have to hack XPI zips to change the manifest to allow installation (the instructions for getting Firefox to ignore version checks are no longer accurate for the latest version). I think they're working on the new extension framework to allow reboot-less installs, etc, but their extension developers aren't adopting them quickly enough.
- wladimir 15y agoHe forgot one: SPDY is a bidirectional protocol, finally asynchronous notifications from server-side can be delivered without hacks such as long-polling or separate connection like websockets. This is long overdue. Huray!
- spokengent 15y agotechnically cool, and under the hood an improvement, but end users won't notice anything different. Comet and websocket work just fine. I'm more interested in browser developments that mean you can do stuff you couldn't before - access to geolocation/multitouch/sound/webcam etc.
- MatthewPhillips 15y agoEnd users might not notice speed improvements, but they do respond to them, according to the data.
- spokengent 15y agoSPDY vs comet may be noticable if you're doing a real time game or something. But SPDY vs websocket should be the same. I'm just saying, it's not "wow you can now do X you couldn't before". It's "Oh they made X a bit faster"
- pjscott 15y agoSPDY also speeds up ordinary page loading.
- MostAwesomeDude 15y agoWebSockets do not work "just fine." Please don't use them.
- Zev 15y agoYou're going to have to give us more than that to go on. Like, you know, an actual downside to using WebSockets?
- udp 15y agoSPDY is indeed always over SSL, but it requires TLS NPN (Next Protocol Negotiation), making it impossible to implement with older versions of OpenSSL or with any version of the Windows SChannel API. This doesn't make it a particularly inviting protocol to use. I'd have to switch my entire SChannel layer for OpenSSL on Windows, and probably link statically to the version of OpenSSL with NPN on *nix.
- yuhong 15y agoYep, the problem is that SChannel is part of Windows, so that it will take a new version of Windows to support it. Hopefully they are planning to implement support in Win8.
- pjscott 15y agoIf your servers support it, and a few major web browsers support it, then SPDY should work for most people. You can always fall back on HTTP, so if 80% of your users speak SPDY, that's a good situation.
- icebraining 15y agoOne thing I dislike about SSL (and SPDY by extension) is that it destroys shared caching. My college has a transparent Squid proxy which they use to block Rapidshare/Megaupload, but also to cache static content, and it does speed them up significantly (latency to the US can be a bitch sometimes). I guess the upsides make up for it, but I have a feeling we wouldn't need CDNs so badly if HTTP caching was used at ISP level.
- viraptor 15y agoBut if they knew what's being requested, then the privacy would not be a part of the system. Unless the whole request was preceded by some signed hash of the request+headers that the cache could use for identification... Then again by doing mitm you could maybe poison the cache with a known content having the same hash (depends on the complexity of solution of course). That seems to get really complicated quite fast.
- deleted 15y ago[deleted]
- icebraining 15y agoThen again by doing mitm you could maybe poison the cache with a known content having the same hash (depends on the complexity of solution of course). That should be almost impossible; I mean, digital signatures (include PGP) are still considered safe, as far as I know.
- viraptor 15y agoWhat I meant is that if it has to be sent outside of the protected stream, it could be also exchanged with mitm. Unless the hash itself is somehow related to the stream in a visible way. That kind of implementation complexity, rather than the signature/hash complecity.
- Zash 15y agoThere is this thing called Stream Control Transmission Protocol (SCTP) already, which does sort of what SPDY does, without breaking the OSI model. Ie multiple concurrent streams over a single session. Not sure how it interacts with SSL/TLS thou.
- asomiv 15y agoGood luck making SCTP work with the $50 routers that everybody has in their homes. While you're at it, will you convince the rest of the world to switch to IPv6 please?
- apaprocki 15y agoWhat has kept SCTP down is the fact that the NAT code would have to be modified to support SCTP connections because they can be multi-homed. That will never happen. So, ironically, once the majority of the world has transitioned to IPv6, SCTP should be theoretically usable to talk to anyone if you're both not behind NAT anymore.
- koenigdavidmj 15y agoYeah, but the cheap consumer routers that do not let SCTP through the NAT do not generally let IPv6 through either.
- Zash 15y agoYeah, this is unfortunately in the same bucket as all the other awesome things we could do if NAT didn't exist :(
- Zash 15y agoGood luck getting everyone to switch from IE6.
- caf 15y agoSPDY is over port 443 because of network discrimination against unusual TCP port numbers - good luck using an entirely different IP protocol number!
- Corrado 15y agoI really like SPDY and welcome including more clients on the bandwagon, but where are the server implementations? Nginx is quite popular as of late but it doesn't plan to implement SPDY any time soon. There is mod-spdy for Apache but it is still experimental and there doesn't seem to be support in IIS or LigHTTPd at all. :(
- angelbob 15y agoThe server implementations are significantly more difficult than the client implementations. And the client implementations aren't easy. Among other problems: * Need an SSL key, which means self-signing, $$, or a monthly update to keep your free key current * Implementing SPDY server-push means explicit dependency lists you currently don't keep * The protocol is young and has changed multiple times * It's binary and hard to test -- it's not always clear where a problem lives Add up those and "oh, my site is fast enough for what I'm doing" and you get a recipe for no good free server implementations. Presumably some larger companies are working on it, but they have to justify that (substantial) effort for improvements only the Chrome portion of their userbase ever see. So at least Firefox supporting SPDY will put more pressure on companies to support it.
- StavrosK 15y agoDoes anyone know how SPDY ensures backward-compatibility? How does an SPDY-enabled browser detect a non-SPDY-enabled server without getting it confused?
- brianpane 15y agoThe way Chrome achieves this backward-compatibility is by using the SSL Next Protocol Negotiation (NPN) extension during SSL handshaking. When the browser is establishing an SSL session, it mentions to the server that it's willing to speak SPDY (as part of the ClientHello message). If the server also speaks SPDY, it can communicate that fact back to the client. If the client sees that the server supports SPDY, it proceeds to send SPDY messages over the newly established connection once the SSL handshaking is complete. Otherwise, it sends HTTP messages. The cool thing about this approach is that it doesn't add any additional network round trips.
- StavrosK 15y agoAh, thanks, I forgot it was all over SSL. I was thinking regular HTTP, which doesn't have a negotiation step before sending the headers.
- deleted 15y ago[deleted]