Wait, so how do I enable it on Chrome? I've gone to:<p>chrome://net-internals/#quic<p>like the slide says, but Chrome just says "QUIC Enabled: false" without any switch to turn it on. (Chrome 32 on OSX.)<p>Edit: turns out the answer is to go to chrome://flags/#enable-quic<p>Also, what web servers support QUIC? Is there some kind of Apache add-on in development? And how will Chrome know whether to try to connect via QUIC or not? If QUIC gets enabled in my Chrome, does this mean Chrome tries to establish both a QUIC and TCP connection to each server always?
Nice! I implemented this same idea in the social network we're launching today (already Apple approved, ready to hit the Release to Store button in just a few minutes).<p>Google's right: it's bloody fast, with zero-latency crypto setup times. We love it. This is terrific tech for mobile devices and high-latency, cellular networks.<p>EDIT: Obviously, I didn't implement QUIC specifically, but something that's equivalent (for our own application). We used NaCl specifically for the cryptography, although there's more to it than just making library calls…
Video of interview/talk: <a href="http://www.youtube.com/watch?v=hQZ-0mXFmk8" rel="nofollow">http://www.youtube.com/watch?v=hQZ-0mXFmk8</a>
although slightly alluded to in the 'parking lot problem' i dont see any reference to mptcp. any reason why ?<p>edit-1: quic geek faq contains some more details (<a href="https://docs.google.com/document/d/1lmL9EF6qKrk7gbazY8bIdvq3Pno2Xj_l_YShP40GLQE/mobilebasic?pli=1" rel="nofollow">https://docs.google.com/document/d/1lmL9EF6qKrk7gbazY8bIdvq3...</a>)