[drdaeman]

While this may be somewhat useful (particularly due to more fine-grained auth), I believe Redis is already being mostly-RESTful as REST is not about transporting data using HTTP. It's - going by Wikipedia list on REST constraitns - client-server (check), mostly stateless (check; states are only for pubsub and transactions), cacheable (uhm... partially), layered (check), and even has code-on-demand features.

[slashdotaccount]

This lark software isn't REST architectural style by the definition that matters (Fielding's).

http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...

No REST without link relations; and fixed resource identifiers go contrary. Nearly all HN submissions that claim to be REST are not, personally I haven't seen a single one in 2013. That's a shame.

[pepve]

Either that, or the developer community has appropriated the term to mean something more generic.

[the1]

yes, REST is same as web scale a.k.a mongodb. Developer community has also appropriated functional programming to mean angular.js. or was that underscore or something.

[meowface]

Could you provide a good example of a fully RESTful API? I've seen lots of comments on HN and other places saying "this is not REST", but I don't really recall one where people said "yep, this is REST."

I'd be curious to see what it should really look like.

[dragonwriter]

> Could you provide a good example of a fully RESTful API?

HTTP/1.1 (Not a particular API built on top of it, but HTTP itself.)

[glassx]

http://atompub.org

http://www.odata.org