Omer Shapira introduces HTTP/2 (and SPDY), exploring the impact the protocol has on application design, and telling the story of LinkedIn adopting SPDY on its network infrastructure.
Benoît Chesneau discusses creating, scaling and reusing HTTP connections, summarizing techniques used to reduce memory usage in Erlang and ways to handle massive client connections efficiently.
Richard Crowley introduces Go standard library's HTTP packages, the relationship between JSON and Go's data structures, and Go's support for reflection, useful to create safe APIs.
Jafar Husain explains how Netflix uses reactive programming to build and consume REST endpoints, and how they work around the limitations of the HTTP protocol to create high-performance REST APIs.
Craig Brozefsky introduces clj-mook which provides a session abstraction for client interactions with a web application based on clj-http, a handful of threading macros, JSoup, and a couple of maps.
Poul-Henning Kamp details some of the current HTTP performance issues that wait to be solved in the future.
Paul Downey explains what they did to redirect all traffic from DirectGov and Business Link to gov.uk, along with the tools, techniques and testing involved for the operation to succeed.
Roberto Peon introduces SPDY which is the starting point for HTTP 2.0, a standard in development, explaining why a new HTTP standard is needed and how SPDY helps.
Guillermo Rauch investigates how some technologies – WebSocket, SPDY, WebRTC, HTTP 2.0 – help with real-time web.
Cesare Pautasso and Guy Pardon propose a way of implementing transactions over HTTP using REST and the Try-Confirm/Cancel protocol.
Subbu Allamaraju discusses interoperability between web applications using ql.io, an Node.js-based HTTP gateway.