Tag: REST

Amazon fails at REST

Designing in side-effects to GET requests is a fundamental mistake of web development that people who don’t understand the web/http tend to make. It’s less common now than it used to be, but I’m suprised to see it in a web API from one the biggest web properties and doubly surprised to see it called “REST”.

what is it with amazons infatuation with SOAP? how can they be a web company yet develop such lousy “API”s?

AJAX and automation

For these 2 reasons — the transparency of the HTTP pipeline, and the accessibility of the JavaScript object model — I think that AJAX is inherently more automatable than conventional GUI apps ever have been.

the view source qualities of RESTy interfaces are only slightly impacted by JSON / XMLHTTP, imho. more problematic: the js obfuscation.

URI Templating

not sure yet how this is relevant, but it is backed by people i trust with webarch

The idea behind URI templates is blindingly simple. There are lots of conventions that people use to denote the variable parts of URIs; one of them is to use {brackets}. All that we’ve done is codify that practice (brackets are a good choice because they’re not allowed in URIs, so there isn’t much risk of collision).

2007-07-28: hopefully leading to more REST hygiene in internet systems