News for hackers. Stuff that matters.
Re:Stabilizing Ember Data by steveklabnik on Saturday March 23, 2013 @08:36AM (#5427891)
AM::S maintainer here!

Conventions are more than just HTTP verbs, and the REST you refer to is... a set of conventions!

If you look at the spec for, say, ATOMpub[1], you'll find a set of conventions on top of REST: "Here's how you retrieve a resource"[2], "here's how you edit a resource"[3], "here's how you delete a resource"[4], among other things. This is because (as I'm sure you know, since you care about REST so much) that HTTP verbs do not map directly to CRUD, and there are verbs that do other things as well, so it's important to say what we mean, exactly.

"Conventions" are just putting a little bit of formalism around communication, so that both parties know what's being discussed. That's _really important_, especially between back ends and front ends. When AM::S spits out conventions-based JSON (there isn't a good name for the format yet), I can be confident that Ember apps will understand what I'm talking about, and that relieves work I'd normally have to do.

1: http://tools.ietf.org/html/rfc5023

2: http://tools.ietf.org/html/rfc5023#section-5.4.1

3: http://tools.ietf.org/html/rfc5023#section-5.4.2

4: http://tools.ietf.org/html/rfc5023#section-5.4.3

There are no comments on this comment yet.