Skip navigation

This is Volume 11 of This week in REST, for Apr 5 2010 – Apr 11 2010. For more information on this blog see this post. Also, from this week there will be a change in the way links for the blog are collected. Since no one except me was contributing links to the REST wiki for the last couple of weeks, from now on I’ll be collecting links myself and if you want a REST-related link included – just e-mail me the links, tweet or leave a comment on the latest blog post.

Around the Web

Why understanding REST is hard and what we should do about it – systematization, models and terminology for REST – Understanding REST is not easy due to the misuse of terminology, lack of formal models and no systematization of knowledge. Plus, a nondeterministic finite state machine formal model of simplified RESTful user-agents.  (by Ivan Zuzak)

A RESTful Hypermedia API in Three Easy Steps – Designing a RESTful API for simple list management in three easy steps. Great tutorial on designing RESTful services. (by Mike Amundsen) – A post on understanding essential properties of REST (with a focus on HATEOAs) in order to apply it as the style for a network of constrained devices. (by Lisa Dussault)

The Central Problem in REST –  Thoughts on using application-specific media-types and problems that causes.

Testing RESTful response types – How to test RESTful response types in Ruby on Rails. (by Jamie Rumbelow)

Steady-State – A summary of interesting recent discussions on REST steady states. (by Jan Algermissen)

REST discussion group

There is no such thing as a REST client!!! – A rant on the misuse of terminology when referring to “REST clients” which is an undefined concept.

Why understanding REST is hard and what we should do about it – A thread for discussing ideas for improving understanding of REST, as proposed in the blog post mentioned above.

How comes to life an “Application” in the sense of Roy’s dissertation? – What exactly is an “application” in terms of REST?

A RESTful Hypermedia API – Thread for following up on the blog post mentioned above (“A RESTful Hypermedia API in Three Easy Steps”).

Interesting tweets

@mamund – “well-designed hypermedia types provide high cohesion (communicational & functional) in a low-coupling, stateless environment. #HTTP #REST

@mamund – “@mike__kelly “@garnaat: Apps need to store state somewhere < yeah, on the client side” <- this hinders access for same user in two locations”

AndrewWahbe – “Do folks have a hard time understanding that the system behind the client can be more complex than the system behind the server?”


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: