4 ms·
I think QUIC is supposed to address this: http://blog.chromium.org/2013/06/experimenting-with-quic.html http://blog.chromium.org/2013/06/experimenting-with-quic
by justinsb 13y ago
I think QUIC is supposed to address this:
http://blog.chromium.org/2013/06/experimenting-with-quic.html http://blog.chromium.org/2013/06/experimenting-with-quic.htm...
- jsnell 13y agoQUIC could address it, but does not automatically do so. Specifically, it fixes the head of line blocking part of the problem. But it will still have a congestion control mechanism, and could be vulnerable to bogus retransmissions (and unnecessary lowering of the congestion window) from the extreme 3G jitter.
- fsiefken 13y agothx, something like that would be great to use over packet radio & gsm. If someone builds a QUIC proxy server service with client to speed up browsing over slow links like Opera does with their always open 'socket' connection we have another choice. The Opera solution is actually quite usable. I wonder if similar performance gains can be achieved by using openvpn with udp with or without ziproxy. If so you wouldn't be locked to chrome or opera.
- gsnedders 13y agoOpera Max is meant to be something like that — a generic VPN that compresses all non-encrypted transfers (which are, of course, increasingly infrequent).
- youngtaff 13y agoMy understanding is QUIC is being used as a proof of concept for protocol experiments - it may be pushed towards standardisation or the the lessons from it may be pushed into other protocols
- dragonwriter 13y agoIsn't that how SPDY started out?
- youngtaff 13y agoIt is but talking to some of the Dev Advocates at Google, they're pretty open that it could go either way - some of the things the QUIC guys have learnt about speeding up TLS negotiations is going information HTTPS stuff (can't remember the exact details) Where QUIC may come into it's own is as as a replacement protocol for things like WebRTC.