HTTP/2 be or not to be

Transcript

1. HTTP/2 be or not to be That is the request By Kenneth GItere
2. Brief history of HTTP - HTTP/ 0.9 - HTTP/ 1.0 - HTTP/ 1.1
3. Shortcomings of HTTP/1.x and how they were solved - Server only responds with what has been requested - A maximum 6 connections from the client to a server - Head of line blocking
4. Server only responds with what has been requested - Inlining resources in HTML - Concatenating assets and minifying them - Image spriting
5. A maximum 6 connections from the client to a server - Domain sharding Head of line blocking couldn’t be hacked around
6. Then came SPDY (pronounced speedy)
8. SPDY - Research project started at Google by Mike Belshe and Rob Peon. - Attracted attention from the HTTP Working Group and served as both a precursor and cornerstone of a potential HTTP/2. In comes HTTP/2 ...
9. In 2015, an official release was due for HTTP/2 and the SPDY project was subsequently going to be shut down. Major browsers all provided support for this protocol and so did services like Akamai and NGINX. But then what is HTTP/2?
10. HTTP/2 - Internet Protocol built on top of TCP - Maintains the same semantics as previous HTTP versions e.g Headers - Features: - Server Push - Client-Server connections happen over streams. - Framing of HTTP requests
11. Features - Server push - The HTTP/2 server pushes (sends) assets/resources the user has not requested. - Can allow for caching of resources - Client-Server connections is over streams - Reduces number of connections to server - Framing of HTTP Requests
12. Binary Framing
13. Additional Features Resource Prioritization
14. Coding Time!!
15. Questions?