By combining the best of both protocols, Google hopes to go further than the SPDY, a basis for future HTTP 2.0. QUIC is implemented in some Prerelease Chrome. Google has implemented a new protocol recently, QUIC (Quick Internet Connections UDP) in the pre-release of the Chrome Canary browser. The protocol, experimental, is seen as a possibility to overcome the limitations of TCP by Google. Noting improvements in version 2.0 of the HTTP standard, based on the SPDY protocol, Google wants to go further. On the blog post announcing QUIC, he explains that it is a protocol under development which should bring improved features TCP, but with UDP transport. This strategy aims to overcome the limitations of the two protocols: the first one UDP faster is not connection oriented. He is unable to control the state of the transmission that allows TCP. But it is less flexible and tends to slow down the connection, Judged Google. Blame it on the audit function of TCP transmissions precisely. Combining the speed of UDP capabilities negotiation, transmission control by a prior connection to sending packets TCP, QUIC has been tested on the server side and since February, client-side on some versions of Chromium. Integration into Chrome Canary must test the protocol in real conditions on some sites. The Google justifies that the conditions for connecting the real world often differ considerably and the in-house testing also. That is why, even if "initial tests are promising," it has yet to test the advantages and disadvantages of QUIC in real conditions. For users, when queries on Google servers where QUIC connection is implemented, no difference will be visible but improved in speed is visible. Among the benefits highlighted by Google include a security level TLS, fast connectivity, control packets to reduce losses, error correction packets to minimize latency, etc. These advances will now be tested, and then hope Google move to the next phase "work with the rest of the community to develop these features and techniques QUIC in standard networks." FAQ and group discussions were provided by Google.
