Gunnar Hillert introduces WebSocket, the protocol and the corresponding W3C API, with an emphasis on the JSR-356 defining the Java EE 7 API.
John Musser, Joe Rago, Augusto Marietti, Steven Willmott, Michael Vizard
Peter Orlowsky provides insights into the strategy choices that created Getty Images’ API program and the customer/business value the API creates.
Many of today’s APIs rely on 3rd party systems, software and services to operate, infrastructure that comes in various flavors. This panel covers these different flavors and how to choose between them.
Giovanni Asproni expands upon the idea that usable APIs help writing clean code.
Irakli Nadareishvili, Jon Moore, and Anthony Cuellar share insight in creating teams and building media APIs for distributing content.
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.
Andrew Mager, Paul Osman, Evan Stein and R. Kevin Nelson share from their experience introducing a music API culture into their companies and developing such APIs.
Stephane Dubois shares insight in Xignite’s road building a business model providing APIs for accessing financial data.
Rickard Oberg explains how to expose use-cases to solve the linking problem in RESTful APIs, and how this will simplify both API development, documentation, as well as client development.
Mike Amundsen describes the ALPS standard, a way to define the data and workflow details for a Web application and apply these details consistently regardless of the media type in use. Working examples in the talk also show how this standardized definition can make designing, implementing, documenting, and maintaining Web APIs easier and more consistent across multiple media types.