Everyone has heard of TCP and UDP, now a new transport layer protocol has been developed by Google, QUIC which stands for 'Quick UDP Internet Connections'.
https://en.wikipedia.org/wiki/QUIC QUIC aims to be nearly equivalent to an independent TCP connection, but with much reduced latency (goal: 0-RTT connectivity overhead) and better SPDY-like stream-multiplexing support. QUIC, with its higher level application protocol elements which multiplexes streams (similarly to SPDY and HTTP/2), can reduce or compress redundant data transmissions (such as headers). As with SPDY, QUIC benefits greatly from this compression, and is generally able to make numerous HTTP(S) requests within a single initial congestion window. QUIC is tightly linked to the TLS/1.3 protocol and shares many negotiation concepts and packets. The OpenSSL team is now looking into QUIC support. The Google Chrome browser has supported versions of QUIC for a few years, as do Google servers, and the IETF has a working group writing specifications. But it will be a while yet before QUIC becomes common. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
