TechCentralTechCentral
    Facebook Twitter YouTube LinkedIn
    Facebook Twitter LinkedIn YouTube
    TechCentralTechCentral
    NEWSLETTER
    • News

      Standard Bank IT spending tops R10-billion in six months

      19 August 2022

      Hungry Prosus to splurge up to R30.7-billion on iFood stake

      19 August 2022

      Koeberg unit shut down due to mechanical fault

      19 August 2022

      Blue Label expects robust full-year earnings growth

      19 August 2022

      Sarb tells banks they should work with crypto exchanges

      18 August 2022
    • World

      15 September pegged as target date for ethereum’s big ‘Merge’

      19 August 2022

      Qualcomm gets serious about servers

      19 August 2022

      China blasts US over ‘discriminatory’ Chips Act

      18 August 2022

      Tencent reports first-ever sales decline

      17 August 2022

      Chip makers are flashing a big warning for the global economy

      17 August 2022
    • In-depth

      Are you a chronic procrastinator? Read this!

      18 August 2022

      Semiconductor boom turns to bust

      16 August 2022

      African unicorn Flutterwave battles fires on multiple fronts

      11 August 2022

      The length of Earth’s days has been increasing – and no one knows why

      7 August 2022

      As Facebook fades, the Mad Men of advertising stage a comeback

      2 August 2022
    • Podcasts

      Qush on infosec: why prevention is always better than cure

      11 August 2022

      e4’s Adri Führi on encouraging more women into tech careers

      10 August 2022

      How South Africa can woo more women into tech

      4 August 2022

      Book and check-in via WhatsApp? FlySafair is on it

      28 July 2022

      Interview: Why Dell’s next-gen PowerEdge servers change the game

      28 July 2022
    • Opinion

      How AI could transform financial services in emerging markets

      19 August 2022

      No reason South Africa should have a shortage of electricity: Ramaphosa

      11 July 2022

      Ntshavheni’s bias against the private sector

      8 July 2022

      South Africa can no longer rely on Eskom alone

      4 July 2022

      Has South Africa’s advertising industry lost its way?

      21 June 2022
    • Company Hubs
      • 1-grid
      • Africa Data Centres
      • Altron Document Solutions
      • Amplitude
      • Atvance Intellect
      • Axiz
      • BOATech
      • CallMiner
      • Digital Generation
      • E4
      • ESET
      • Euphoria Telecom
      • IBM
      • Kyocera Document Solutions
      • Microsoft
      • Nutanix
      • One Trust
      • Pinnacle
      • Skybox Security
      • SkyWire
      • Tarsus on Demand
      • Videri Digital
      • Zendesk
    • Sections
      • Banking
      • Broadcasting and Media
      • Cloud computing
      • Consumer electronics
      • Cryptocurrencies
      • Education and skills
      • Energy
      • Fintech
      • Information security
      • Internet and connectivity
      • Internet of Things
      • Investment
      • IT services
      • Motoring and transport
      • Public sector
      • Science
      • Social media
      • Talent and leadership
      • Telecoms
    • Advertise
    TechCentralTechCentral
    Home»In-depth»Big upgrade promises much speedier Web

    Big upgrade promises much speedier Web

    In-depth By The Conversation20 February 2015
    Facebook Twitter LinkedIn WhatsApp Telegram Email

    URL-640

    The Hypertext Transfer Protocol, or HTTP, is a key component of the World Wide Web. It is the communications layer through which Web browsers request Web pages from Web servers and with which Web servers respond with the contents of the page. Like much of the Internet, it’s been around for decades, but a recent announcement reveals that HTTP/2 the first major update in 15 years is about to arrive.

    The original HTTP protocol was the protocol first used by Sir Tim Berners-Lee at Cern where the Web was created in 1991. This was improved over many years and finalised as HTTP 1.1 in 1999, the current standard used worldwide. Over the years, the Web has changed dramatically, introducing images, complex style sheets and Javascript code, Flash and other embedded elements and more. The original HTTP was a simple protocol for a simple Web, it was not designed to handle increasingly media-rich websites.

    For example, Google handles 40 000 Web searches per second every day. To handle the pressure of serving billions of Internet users, the company’s technicians launched a project in 2009 called SPDY (pronounced “speedy”) to improve HTTP. Originally only for internal use, other sites fielding heavy traffic such as Twitter, Facebook, WordPress and CloudFlare also implemented SPDY having seen its performance improvements.

    This caught the attention of the Internet Engineering Task Force (IETF), which develops and promotes Internet standards. IETF decided to use SPDY as the basis for HTTP/2 in 2012 — and the two protocols were developed in parallel. Even though Google spearheaded the protocol’s development, the work is continued by the IETF’s open working groups as it has done for other protocols for more than 30 years.

    Google recently announced it was dropping SPDY in favour of the soon-to-arrive HTTP/2.

    Web pages today can generate many requests for images, CSS style sheets, video and other embedded objects, off-site adverts, and so on — perhaps a hundred of these per page. This adds unnecessary strain to the Web server and slows the Web page loading time because HTTP 1.1 only supports one request per connection.

    HTTP 1.1 is sensitive to high-latency connections — those with a slow response time. This can be a big problem when working on a mobile device using cellular networks, where even a high-speed connection can feel slow. HTTP pipelining allows the browser to send another request while waiting for the response of a previous request. While this would go some way to tackling high latency, it is susceptible to problems of its own and is disabled by default in most browsers.

    Rather than using clear text, HTTP/2 is now a binary protocol, which is quicker to parse and more compact in transmission. While HTTP 1.1 had four different ways to handle a message, HTTP/2 reduces this to one. To tackle the multiple request issue, HTTP/2 allows only one connection per site. But using stream multiplexing fits many requests into a single connection. These streams are also bidirectional, which allows both the Web server and browser to transmit within a single connection. Each stream can be prioritised, so browsers are able to determine which image is the most important, or prioritise a new set of streams when you change between browser tabs.

    HTTP is a stateless protocol — every connection comprises a request-response pair unconnected to any connections before or after. This means every request must also include any relevant data about the connection — this is sent in HTTP headers. As HTTP 1.1 evolved, the headers have grown larger as they incorporate new features. HTTP/2 uses header compression to shrink this overhead and speed up the connection, while improving security.

    A final addition is server push. When a Web page is requested, the server sends back the page, but must wait for the Web browser to parse the page’s HTML and issue further requests for things it find in the code, such as images. Server push allows the server to send all the resources associated with a page when the page is requested, without waiting. This will cut a lot of the latency associated with Web connections.

    Once Web servers and Web browsers start implementing HTTP/2 — which could be as soon as a few weeks from now — the Web browsing experience will feel quicker and more responsive. It will also make developers’ lives easier by not having to work around the limitations of HTTP 1.1.

    In fact, some of the latest versions of popular browsers (Firefox 36, Chrome 40 and Internet Explorer 11) already support HTTP/2. For Chrome and Firefox, HTTP/2 will be used only over encrypted connections (SSL) — this, along with the Let’s Encrypt initiative, will probably boost the adoption of encryption more widely.The Conversation

    • Peter Maynard is PhD researcher in network security systems at Queen’s University Belfast
    • This article was originally published on The Conversation
    Firefox Google Microsoft Peter Maynard Tim Berners-Lee
    Share. Facebook Twitter LinkedIn WhatsApp Telegram Email
    Previous ArticleReal whodunnit in hard drive malware case
    Next Article SA’s parliament of paranoia

    Related Posts

    Are you a chronic procrastinator? Read this!

    18 August 2022

    Google buys into African e-logistics firm Lori Systems

    17 August 2022

    Acrobat Sign and Microsoft accelerate digital transformation

    17 August 2022
    Add A Comment

    Comments are closed.

    Promoted

    Does your contact centre have the CX factor?

    19 August 2022

    Entelek, A2pay to roll out 2 500 free Wi-Fi sites in South Africa

    18 August 2022

    Companies are drowning in data – but solutions are at hand

    18 August 2022
    Opinion

    How AI could transform financial services in emerging markets

    19 August 2022

    No reason South Africa should have a shortage of electricity: Ramaphosa

    11 July 2022

    Ntshavheni’s bias against the private sector

    8 July 2022

    Subscribe to Updates

    Get the best South African technology news and analysis delivered to your e-mail inbox every morning.

    © 2009 - 2022 NewsCentral Media

    Type above and press Enter to search. Press Esc to cancel.