Todd Brackley

Todd Brackley

Todd actively works with startups (and corporates if he has to) to leverage a REST style of architecture to effectively solve business and IT problems. He is a co-founder of Hypr.

This is Todd's first RESTFest and coming all the way over from New Zealand Aotearoa is really interested in seeing what others are up to (in practice).

• http://twitter.com/toddbNZ
• http://linkedin.com/in/toddbrackley

Proposed Talks

The Humble Browser Challenge (to the server): my top ten tests

• Type: 5in5
• Level: All
• Description: There is a current anti-pattern occurring in implementing hypermedia APIs. That “REST” clients must be coded into the browser—for example, as a plugin specific to the media type. It’s an optimisation (and optimisations are needed but not as the baseline). The anti-pattern is not the client per se but rather the server. The client needs to compensate for the server not being RESTful—so you put “more REST” into the client. Based on this insight, the generic, humble browser is therefore a perfect client to start measuring the REST level of the server that the API wants to support. So I thought that I'd list my top ten ways to measure how well your API is going.
• Background: A browser with addons: header negotiation and JSON viewing and clicking
• Material covered: Humble Browser as a test of webbyness/restyness
• Links: Setting up the Humble Browser for a Hypermedia API
• Video: The Humble Browser across an API

Provisioning vs in-place editing on a hypermedia client

• Type: StackDay
• Level: All
• Description: A hypermedia client walks a network of data - that we all know. I'm wondering if people are making the distinction between provisioning (synchronising a graph of resources) and in-place editing (update/create a single resource). I will demonstrate this distinction in a javascript client: provisioning via drag-n-drop where you drag out an entire network of data and drag it back to create or update; in-place edits are just as you expect as forms on a page. I will discuss how provisioning in this style has been important for a strangler-application-style refactoring we've been doing for a customer.
• Background: None
• Slides: Web browser as a test of API RESTy-ness level