Paul Downey talks on the current status of identity management on the web covering cross-site challenges, REST, HTTPS, Open ID, all in the context of enterprise architecture.
Justin Sheehy details Webmachine, a RESTful toolkit for writing well-behaved HTTP applications, helping developers to deal with the complexities of an HTTP-based application.
Glenn Block presents how developers can build RESTful solutions using Microsoft’s technologies, especially with WCF and .NET.
Scott Davis makes a case for semantic data, pointing out that it is currently used by major websites to improve their traffic, presenting 2 ways to add metadata to a document: RDFa and microformats.
Ian Robinson: the web is counterintuitive because clients are interested only in URIs and they are responsible for requests’ sequence, and one should use protocol resources , not domain resources.
Cesare Pautasso presents a design methodology for RESTful services based on several patterns: Uniform Contract, Entity Endpoint, Content Negotiation, Endpoint Redirection, Idempotent Capability.
Stefan Tilkov offers guidelines for the architect looking for a solution to his problem. Should it be a generic or a specific one? He compares several such solutions outlining the pros and cons.
In this presentation, recorded at QCon San Francisco, ThoughtWorks' Ian Robinson explains how a RESTful HTTP approach, using many advanced Web concepts, can be applied in an Enterprise project.
In this QCon presentation, HTTPbis WG chair Mark Nottingham gives an update on the current status of the HTTP protocol in the wild, and the ongoing work to clarify the HTTP specification.
In this talk, recorded at QCon London 2008, Steve Vinoski explains how a RESTful architecture can further reuse in unforeseen circumstances.
In this presentation, recorded at QCon, WSO2's CEO and WSDL co-inventor Sanjiva Weerawarana tries to address some of the truths, myths and lies surrounding the REST-vs.-WS-* debate.
The web is rocking the world of developers. Hence, at Microsoft, they are trying to stretch the .NET framework to cover the Cloud such that applications can be developed and run anywhere.