Mark Wolfe provides examples of protocols that can be used to build web applications, and reviews the pros and cons of doing so.
Brian Cavalier shows how Differential Synchronization can be used with JSON Patch to synchronize application data between clients and servers over HTTP Patch, WebSocket, and STOMP.
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.
Gunnar Hillert introduces WebSocket, the protocol and the corresponding W3C API, with an emphasis on the JSR-356 defining the Java EE 7 API.
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.
David Rogers outlines how a highly-scalable RDF and SPARQL-based API was delivered, how a graph of highly-connected data can be managed effectively across a large organization, and more.