Skip navigation

This is Volume 16 of This week in REST, for May 10 2010 – May 16 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

Resource Oriented Programming – A nice overview of REST principles (under the term “Resource oriented programming”) and how these principles are exemplified in Persevere 2.0, in its object store framework, Perstore, and its web stack Pintura. (by Kris Zyp)

Modeling – Architectural Styles – What is an “architectural style” anway? (by Arnon Rotem-Gal-Oz)

Resource Lifecycles and REST – On resource lifecycles and and a self high-5 by the author for recognizing them in REST 3 years ago. (by Jean-Jacques Dubray)

Expressing Service Capabilities Uniformly – (video) Recording of a very interesting talk on “reaching SOA integration maturity using reusable and uniform contracts translated into REST service definitions by splitting capabilities into centralized methods, choosing proper media types and using service-specific resource identifiers”. (by Benjamin Carlyle)

Link Header-based Invalidation of Caches – A blog-version of the authors research paper presented on WS-REST 2010 concerning the proposed use of the HTTP Link: headers to maximize the efficiency of gateway (or reverse proxy) caching mechanism. (by Mike Kelly)

Selecting a WG document for CoAP – A thread on the IETF CoRE WG (Constrained RESTful Environments) mailing list discussing the selection of the WG document, touching upon several key principles of REST.

REST discussion group

How to publish – Ideas on RESTful drafting and publishing of blog posts.

Googles Partial Response and Updates – Thoughts on the two new features in the Google Data Protocol – partial response and partial update.

PUT/POST content type hints – “What are some general guidelines for giving a client hints about what sort of data to supply to a resource which responds to POST or PUT?”

How to design a RESTful collection resource? – Thoughts on designing a collection resource that supports adding and removing multiple items.

RDF as IDL for M2M – A longish explanation of a cool idea for using RDF for M2M.


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: