http

Everything you need to know about HTTP/2

A major change is coming to one of the standards of the Internet. An update to the Hypertext Transfer Protocol (HTTP)—known as HTTP/2—has been finalized and is in the process of being standardized, according to chair of the Internet Engineering Task Force’s (IETF) HTTP Working Group Mark Nottingham.

So… that was a lot of big words and industry terms. Let’s break this down.

You know how you get annoying pop-up messages telling you to update a program on your computer? Well those messages have been flashing for the IETF for some time now. Once HTTP/2 is officially published, it will mark the first major update to the protocol since the adoption of HTTP 1.1 in 1999.

For the average Internet user, this may seem a little technical. After all, HTTP has become so formalized that we don’t even have to type it in to get to a site; it’s the support beams hidden behind the wall of the Web. But this is actually a big deal for the Internet, and you probably have questions. We have your answers.

What does this mean for me?

Basically, it’s all going to get faster. Stenberg told us that the goal of HTTP/2 is to end up with “sites that load and render faster and that can be more responsive when you interact with them.” The new protocol will allow websites to better take advantage of the increased bandwidth provided by faster Internet speeds. This means sites with tons of images, videos, of everyone’s favorite bandwidth eater, the GIF, will load quicker.

Sort of like from this…

To this. 

This will also greatly benefit mobile users, who are often slowed by the limitations of mobile broadband and the time it takes for the connection to process each individual request. Requesting multiple items at a time should help to reduce the wait. “Sites far away, with high latencies, will benefit a lot,” Stenberg said.

Get the answers to all your HTTP/2 questions here

Despúes de 15 años, el Protocolo de Transferencia de Hypertexto se renueva (el famoso http, que le da el principio de su nombre a todos las direcciones de internet que conocemos). Y la verdad ya se había tardado.
Existen muchas buenas razones de que esto suceda, aunque para muchos solo signifique una cosa: harder, better, faster, stronger porn streaming…

Have you heard? HTTP/2 is finally finished. That means that pretty soon webpages will load faster; connections will last longer; servers will respond to requests with more content. What’s not to like! But hold on a sec: What the heck is HTTP/2, again?

Put simply, HTTP/2 is a very overdue upgrade to Hypertext Transfer Protocol, the basic protocol that handles connections between a web server and your browser. The original development of HTTP happened way back when Tim Berners Lee first imagined his World Wide Web project in the late 1980s. However the version of the protocol we currently use, HTTP/1.1, was officially introduced in 1999. Needless to say, the web has changed quite a bit in the past 15 years.

HTTP/2, like any good upgrade, will address some issues with the previous version, and as a result, your web browser will load pages more quickly. This is exciting—but it’s also rather revealing in terms of web history. As the internet’s evolved, web pages have steadily increased in size, like, a lot. Here’s a graph showing the increase from the end of 2010 to today.

The way that HTTP/1.0 and subsequent version of the protocol is designed, the increased page size means more requests sent out “on the wire,” the more data gets duplicated, and the more duplicated data means more congestion on the network. Ultimately, your browser has to work harder, constantly issuing requests for more data, so that you can surf the web watching wacky science videos or listening to tropical house music or whatever it is you do on the web. Enter HTTP/2. Developed by the Hypertext Transfer Protocol working group of the Internet Engineering Task Force (IETF), this new version offers a laundry list of solutions to decrease latency in order to improve page load speed. That was the main goal. Inspired by Google’s SPDY protocol—which is more or less a way to hack HTTP—the new HTTP/2 protocol set out to do away with that multiple connections approach and use a single connection that wouldn’t monopolize network resources…

http://bit.ly/1JsdSfD

What you need to Know about HTTP/2
HTTP/2 idea came into web engineer’s mind by successful presentation of Google’s SPDY project.

HTTP/2 is developed to deliver web page more fast by decreasing the page load time.

How HTTP/2 works?

Constant Connection : HTTP/2 delivers constant connection between client (web/mobile browser) and server that decreases page load time plus it reduce the amount of data being transferred.

Binary Language : It transfer of data in binary language rather then textual format, so computer don’t need to waste time to translate text data into binary format.

Multiplexing: HTTP/2 can send & receive multiple message/data at same time, additionally it also gives features.
  • Prioritization : Priority based data transmission, important data will transfer first.
  • Compression : It compress the size of data into smaller pieces.
  • Server Push : Server makes a pre-guess about the next request & send data.


Check the images below that shows clear difference of page load time between HTTP and HTTP/2.

Image 1: HTTP Load time

Image 2: HTTP/2 Load Time


There is no such real start date of HTTP/2, but study found many website admins are using it unknowingly.

HTTP/2 is already created for many web servers and browser (Chrome. Internet Explorer, Mozilla Firefox) but it still in draft.In layman’s terms, what is HTTP/2 all about and how ,exactly, is it different from the current HTTP?
Νέο άρθρο δημοσιεύθηκε στο ΕΣΠΕΡΙΝΟΣ ☦

New Post has been published on http://esperinos.gr/%ce%b1%ce%b3%ce%af%ce%b1-wulfthrith/

Αγία Wulfthrith

Αγία Wulfthrith
(Κοίμηση 998)
Ηγουμένη του Wilton-Αγγλία
Κοίμηση: 22 Ιουλίου του 998

Η Wulfthrith ήταν μέλος μιας αριστοκρατικής Αγγλοσαξονικής οικογένειας η οποία έγινε μοναχή στο Wilton, λαμβάνοντας το μοναχικό σχήμα από τα χέρια του αγίου Aethelwold, επισκόπου του Winchester. Εκεί, την βίασε ο βασιλιάς Edgar ο Ειρηνοποιός και έπειτα γέννησε την αγία Edith του Wilton. Μεγάλο ήταν το σκάνδαλο, γιατί έπρεπε να υπάρχει σεβασμός προς το μοναχικό ένδυμα. Ο Αρχιεπίσκοπος του Canterbury, ο άγιος Dunstan, καταδίκασε τον βασιλιά απαγορεύοντας του να φοράει την κορόνα του για εφτά χρόνια. Μετά τον θάνατο της γυναίκας του, ο Edgar προσπάθησε να πείσει την Wulfthrith να εγκαταλείψει την μοναστική κοινότητα και να τον παντρευτεί, όμως εκείνη προτίμησε να μείνει μαζί με την κόρη της στο Wilton όπου έκανε τέτοια πρόοδο σε όλες τις αρετές ώστε την επέλεξαν σαν ηγουμένη και τελικά την τίμησαν σαν αγία.

Αγγλικό κείμενο http://www.britannia.com/bios/saints/wulfthrith.html

Μετάφραση orthodoxy-rainbow

από: orthodoxy-rainbow