Instead, HTTP/2 modifies how the data is formatted (framed) and transported between the client and server, both of which manage the entire process, and hides all the complexity from our applications within the new framing layer. All the core concepts, such as HTTP methods, status codes, URIs, and header fields, remain in place. ![]() HTTP/2 does not modify the application semantics of HTTP in any way. To implement these requirements, there is a large supporting cast of other protocol enhancements, such as new flow control, error handling, and upgrade mechanisms, but these are the most important features that every web developer should understand and leverage in their applications. The primary goals for HTTP/2 are to reduce latency by enabling full request and response multiplexing, minimize protocol overhead via efficient compression of HTTP header fields, and add support for request prioritization and server push. Even better, it also opens up a number of entirely new opportunities to optimize our applications and improve performance! HTTP/2 will make our applications faster, simpler, and more robust - a rare combination - by allowing us to undo many of the HTTP/1.1 workarounds previously done within our applications and address these concerns within the transport layer itself. ![]() For full version and related content, see. The following content is an excerpt from High Performance Browser Networking (O'Reilly, Ilya Grigorik).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |