I did not want to comment on DesdeLinux about what is coming with HTTP / 2 mainly because I still do not know all its benefits, which with the little I have read, seem to be many. However, since the boys of Mozilla have included their support in Firefox version 36 that although it has not yet been announced, it can already be downloaded from the FTP.
What is HTTP / 2?
Hypertext Transfer Protocol o HTTP as we know it best, it is the protocol that allows transactions in the World Wide Web (www). HTTP defines the syntax and semantics used by servers, browsers, and more. Can get more detailed information in Wikipedia.
The problem with this protocol is that it is older than Methuselah, and its last revision was in 1999. That is why the working group Hypertext Transfer Protocol Encore (httpbis) of the IETF (The Internet Engineering Task Force) took as a basis SPDY (speedy), a protocol developed by Google in 2009, and after hard work in collaboration with the engineers of Mountain View, have declared HTTP / 2 as a terminated protocol.
Advantages of HTTP / 2 over HTTP / 1.1
But finally, let's go to the advantages that HTTP / 2 brings over the old HTTP / 1.1:
Asynchronous connection multiplexing: HTTP / 2 can be used in parallel, regardless of the number of requests, thus allowing a greater number of requests, which in turn generate more responses for each request at the same time. This protocol has been designed to be used in sites with high levels of traffic, preventing them from colliding, which leads us to the second advantage.
Header compression and request-response pipelining: As HTTP request headers are compressed, less bandwidth is required. Therefore the load will be much faster and many more simultaneous requests can be sent at the same time.
Encryption: This feature was imposed by Firefox and Google Chrome to adopt the new protocol, which means that in the not too distant future, we will see many more sites using secure connections.
In summary, what interests us is that with HTTP / 2 we will be able to browse our favorite websites much faster, without them crashing, especially from mobile devices that have (or had) less RAM memory than a computer.
What does Firefox 36 bring us?
Well, Firefox 36 brings us support for HTTP / 2 (which has not been implemented yet, at least not globally), Media Source Extensions (MSEs) to handle the native reproductions in HTML5 in Youtube, corrections in HTML5, synchronization of the shortcuts in the new tab, new way to see the Preferences and more, many more things that can see here.
If you don't want to wait for it to be included in your header distribution, here are the links:
Note: Google Chrome also has support for HTTP / 2
Testing Firefox 36 😛
Here from Windows everything OK (waiting for Iceweasel 36 to come out tomorrow). Finally the videos on Youtube play well, but for now Firefox saves me from the dash.
Testing Iceweasel 36 from Debian Wheezy. Apparently, it still uses GStreamer to play videos in H.264, the MSE did not implement it and the EME disabled it (thank goodness), and the joke is that YouTube does not automatically launch the player in HTML5 and continues to fallback to the Flash Player.
Anyway, here is the Iceweasel 36 changelog.
I have a question about Asynchronous Connection Multiplexing
This will not have a negative impact on security, due to ddos-type attacks, or simply that "limited" servers are more easily dumped.
That is the concern I have at the moment.
f5 f5 f5 and kabum !!! you no longer need loic to drop the friend server 😀
On the contrary, multiplexing will allow the servers to handle a greater number of simultaneous concurrent connections making use of this technique, since for each real connection in HTTP2 server-client, several data streams can be handled under a certain control system. It is not that multiple connections are magically opened (which is precisely what happens now, in which when opening a page multiple HTTP connections are opened to load its content), but that the same and only connection will allow you to enjoy multiple data flows and services.
The best example that multiplexing techniques work is in telephony, where it has been using this technique for years to increase the number of connections per radiobase and at the same time increase their speeds, understand that; 2G, 3G and 4G have systems that make intensive use of this type of technique.
Well now let's wait for this to become standard and for nginx and the rest to implement it on the server side. These protocol upgrades are exciting and we would like them for now but they have been a long time coming.
Well, from NGinx I don't think there is any problem: http://www.serverwatch.com/server-news/nginx-gearing-up-for-http2.html
Note: Google Chrome also has support for HTTP / 2
So they have http2 too: Opera, Chromium, Maxthon, and the long ETC. that use the Chrome engine right? ...
Good for FF for not falling behind in this regard.
Exact! Or at least in theory.
Hi Elav!
Maybe it's a misinterpretation of mine.
"In summary, what interests us is that with HTTP / 2 we will be able to browse our favorite websites much faster, without them crashing, especially from mobile devices that have (or had) less RAM memory than a computer."
What impact does having more or less RAM have on what the transfer speed means for the HTTP / 2 protocol?
Do you mean that since there is less data downloaded, it will take up less memory? But I have not understood.
Hug!
I have understood something like that too. It is assumed that the higher the content processing, due to the rendering issue, the higher the consumption of the client's resources. Or that's what I understand about all this 😀
Did Mozilla fix the memory consumption problem?
Regards. You have a solution here:
http://www.ubuntuleon.com/2015/02/en-busca-de-la-cache-de-fuego-aka.html
Apparently, yes, since I'm testing it from my netbook and it runs just as smoothly as Opera Blink on the Windows partition. Tomorrow Iceweasel 36 will be available, and I'll tell you in detail how it turned out.
I have been trying iceweasel 36 for some time and there are a couple of things that I am not liking.
1. The first is the appearance of advertising in Hello, with logos that are not open source and without the possibility of choosing to see them or not. That is, although the firefox or iceweasel packages do not bring the images of the logos, the browser when loading them incorporates them without giving you any choice, which could lead to questioning their location in the man repositories of the firefox package.
2. The second is related to the search engine, if one clicks on the magnifying glass and there is no text, the menu with the different search engines does not appear, in addition, after doing a search it returns to the default search engine, which in certain point is annoying and cumbersome.
According to the first point, although let me tell you that Firefox Hello uses web technology and since it is the Mozilla server that is used in Iceweasel, it is practically impossible to remove the logo of the sponsor (which is Telefónica).
On the other hand, I see that they have removed the logo in the search region, since in previous versions they have had problems showing the logo (both on the default homepage and also in the "new tab" part), in addition to lacking the MSE system and the H.264 codec provided by CISCO (thank goodness that YouTube can be configured to view HTML5 by default).
And one thing: it no longer uses the VP8 codec by default, but uses the GStreamer to play H.264 videos in the HTML5 player on Youtube (Why don't you use the VP9 codec?).
PS: The previous comment I was branded as spam. Better was the akismet.
Excellent news
incredible how technology advances