Google's Web is QUIC and SPDY

Subject: Editorial, General Tech | July 2, 2013 - 02:12 AM |
Tagged: google, spdy, QUIC

It missed being a recursive acronym by a single letter...

TCP is known for being the go-to protocol for stable connections over the internet. There are some things you can guarantee: you will not lose bits of data, packets will arrive in order, incorrect packets will be checked and redelivered, and both endpoints will be roughly metered to the least capacity. It is easy to develop applications around the TCP protocol, it does the hard problems for you.

Being meticulous also makes it slow, relatively speaking.

9-ethernet2.png

UDP, on the other hand, frees its packets in a fountain to hopefully land where it is intended. This protocol is fast, but a pain for applications that need some level of reliability. Quick UDP Internet Connections (QUIC), from Google, leverages UDP to create multiple independent, even encrypted connections. While TCP could be made faster, it is beyond the jurisdiction of web browsers; support is embedded into the operating system itself. This leaves building upon UDP, suffering with TCP, or not being compatible with about every network hardware installed just about anywhere.

This comes on the heels of SPDY, Google's other open protocol. SPDY is built around HTTP and both presume a reliable protocol underneath, where TCP is the usual candidate. A large advantage of SPDY allows assets to simultaneously stream over a single connection. TCP will, unfortunately, freeze the entire connection (and thus each stream) when a single stream drops a packet. QUIC, based upon UDP, can then be used to accelerate SPDY further by allowing truly independent multiplexing.

QUIC will be used for "a small percentage of Chrome dev and canary channel traffic to some Google server", for experimentation purposes. The code itself is licensed under BSD and, as such, could migrate to other browsers in due time.

Source: CNet

Getting TCP out of the strange loop it is stuck in

Subject: General Tech | June 14, 2011 - 12:02 PM |
Tagged: http, tcp, spdy, Internet

Google has been working on SPDY, a new protocol which is intended to speed up HTTP without forcing changes to existing websites or protocols.  This application-layer protocol sits between HTTP and TCP, replacing neither instead translating for the application layer and the transport layer to optimize certain parts of the transaction.  Specifically they hope to allow multiple connections over TCP, something that up until now is provided by a workaround in the browser which creates parallel connections as well as getting servers to push data to clients more effectively.  They are also working to reduce latency by reducing the size of the headers that are transported which will be very important in the near future, not only as a way to speed up SSL connections but to help with the increased size of IPv6 headers. 

Up until now SPDY has only been available for Chrome and even then only for certain Google sites which utilize the new translation protocol.  Now Strangeloop is offering an online service as well as hardware which will allow you to implement SPDY without the need to change your website or host.  The Register covers the long overdue change to TCP here.

speedy-gonzales.jpg

"Strangeloop – a Vancouver-based outfit offering an online service for accelerating website load times – has embraced Google's SPDY project, a new application-layer protocol designed to significantly improve the speed of good ol' HTTP."

Here is some more Tech News from around the web:

Tech Talk

Source: The Register