Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
http://www.rubyconf.org.au HTTP/2 is here. The first major revision since 1997 to Hypertext Transfer Protocol on which so much of the modern information transfer relies, HTTP/2 could have an enormous impact on the way we write applications.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "Ruby, HTTP/2 and You" presented by Hiro Asari at RubyConf AU 2017 delves into the evolution of the Hypertext Transfer Protocol (HTTP) and introduces HTTP/2, emphasizing its significance for Ruby developers. The presentation begins by tracing the origins of the web, initiated by Tim Berners-Lee in 1989, and outlines the transition from early protocols like Gopher to HTTP 1.0 and ultimately HTTP 1.1. ### Key Points Discussed: - **HTTP History:** - Introduction of Tim Berners-Lee and the concept of linking documents. - Development through HTTP 1.0 (1996) and HTTP 1.1 (1999), detailing how requests and server responses evolved over time. - **Characteristics of HTTP 1.1:** - Plain text headers and TCP connection reuse enhance performance. - Requests are queued by the server, necessitating careful optimization of resource requests by developers. - **Overview of HTTP/2:** - HTTP/2, or H2, is based on Google’s SPDY protocol, introduced in 2009 and standardized in 2015. - Key features include binary headers, header compression via HPACK, and full duplex operations which improve communication between clients and servers. - **Benefits of H2:** - Supports multiple connections, allowing for simultaneous request handling without blocking. - Server push capabilities enable servers to send resources to clients proactively. - **Tooling and Implementation:** - Major browsers (Chrome, Firefox, etc.) support H2, but command-line tools like cURL are still developing their H2 support. - Developers can utilize CDN for asset delivery and minimize DNS lookups to boost performance. - **When Implementing H2 in Ruby:** - Recommendations include using Rack-based frameworks (Rails, Sinatra) and considering the limitations of current implementations. - Existing Ruby libraries for H2 include ‘http2’ and ‘DS9’, with emphasis on developing fallback logic for handling downgrades to HTTP/1.1. ### Conclusions and Takeaways: - Developers are encouraged to adopt best practices for both HTTP/1.1 and H2 to ensure optimal performance. - The presentation highlights that ongoing developments in H2 integration into Ruby frameworks are essential for leveraging its full potential for future applications. By understanding the features and advantages of HTTP/2, developers can prepare for enhanced performance in their web applications.
Suggest modifications
Cancel