In June 2009, Google engineers explained that many of the Internet
protocols were developed at a time when dial-up connection predominated.
These protocols are not optimized for ADSL today. Google wanted to
thereby form a working group which will be working on HTTP and TCP/IP
protocols.
In November 2009, Google introduced the SPDY, a transfer protocol on the Internet would be two times faster than traditional HTTP. Unlike the HTTP protocol that sends each request for all items on the page (CSS, images, JavaScript) SPDY compresses all upstream. This would result in an average time saving of 55%.
At present, in order to circumvent the limitations of TCP, the browser opens multiple parallel connections, a mechanism that would result in yet more latency. When a new connection is made, the machine is sending three packets to check it and ensure communication with the server. Google proposes to increase the number of packets to 10 to immediately send a complete HTTP request, which may be executed without waiting for a confirmation back from the server.
Within the mechanism to control network congestion, by default, TCP port waits 3 seconds for the confirmation of the server. If no return is made, the transmitted data is considered lost and a new request is sent to retrieve them. Google explains that this waiting time was justified at the time of the Internet Lite and desired to reduce it to 1 second.
In November 2009, Google introduced the SPDY, a transfer protocol on the Internet would be two times faster than traditional HTTP. Unlike the HTTP protocol that sends each request for all items on the page (CSS, images, JavaScript) SPDY compresses all upstream. This would result in an average time saving of 55%.
At present, in order to circumvent the limitations of TCP, the browser opens multiple parallel connections, a mechanism that would result in yet more latency. When a new connection is made, the machine is sending three packets to check it and ensure communication with the server. Google proposes to increase the number of packets to 10 to immediately send a complete HTTP request, which may be executed without waiting for a confirmation back from the server.
Within the mechanism to control network congestion, by default, TCP port waits 3 seconds for the confirmation of the server. If no return is made, the transmitted data is considered lost and a new request is sent to retrieve them. Google explains that this waiting time was justified at the time of the Internet Lite and desired to reduce it to 1 second.
The main problem is that Google cannot go ahead and change how TCP works
as it is a standard used around the world. The research they have done
will need to be reviewed, approved, and when done it will gradually be
implemented on various routers and other equipment.
No comments:
Post a Comment