Skip navigation

This is Volume 22 of This week in REST, for Jul 13 2010 – Jul 25 2010. For more information on this blog see this post. If I missed an interesting blog post, discussion or paper – just e-mail me the links, tweet or leave a comment on the latest blog post. Thanks!

Around the Web

Turbo charging front-end development with user-created RESTful resources – Introduction to RESTx, “an open source project for the creation of RESTful resources”. (by Juergen Brendel)

Steve Vinoski on Erlang and Rest – “Steve Vinoski talks about Rest and Erlang and about what got him convinced in these technologies. He discuses benefits of adopting them in terms of productivity and other aarchitectural properties.” (by Steve Vinoski and Sadek Drobi)

why WADL when you can RUN? – On the advantages and disadvantages of using hypermedia media types over non-hypermedia media types when building distributed applications. (by Mike Amundsen)

Self-Descriptive Hypermedia – An excellent explanation and discussion of what is meant by “self-descriptive” in the context of REST data formats. (by Andrew Wahbe)

Trying to Explain App State for REST – An explanation of the difference between application and resource state using BlackJack as a metaphor. (by William Martinez Pomares)

What if you need Transactions and also REST? – Thoughts on implementing transactions in RESTful systems. (by William Martinez Pomares)

Software libraries

RESTEasy – Version 2.0.0 of the RESTEasy framework has been released.

REST discussion group

PUT for create – Is using PUT RESTful with regart to HATEOAS or should POST be used?

An example paleo-REST application w/ m2m – A description of an application to show that “saying REST/NOT REST is not a value judgement. Infact, sometimes, for something to be RESTful can be a mistake.”

WADL as an hypertext – Lengthy but useful discussion on whether WADL can be used as a hypertext format.

A standardized way to describe a new hypermedia format? – “wouldn’t it be nice if we could agree on THE standard way to describe a link in JSON? Or in XML? And then strive to always use this?”. Well, would it?

HTTP reliability – in order msg delivery? – What if you needed in-order message delivery in your application?

Synchronization of collection resources – How does a client know if a state of a collection of resources changed since it last interacted with the collection?

Interesting tweets

@AndrewWahbe – “@pkeane IMO hypermedia works by providing run-time mapping from client domain (in HTML – interactive info presentation) to service domain”

@wmartinez – “REST. “We are putting too much importance into URIs, when they are simply names referring to the really important guy, the resource.””

@sallamar – “And, ultimately there was vehement agreement that REST != XML/HTTP. Guess when we will conclude that REST != JSON/HTTP?”

@pkeane – “Is json served w/ a link header pointing to js template that turns it into HTML hypermedia? (real question, not rhetorical)”

@assaf – “@sallamar browsers work because of the immense computational power situated between keyboard and chair. APIs don’t have that capacity.”


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: