Is there a Write Side to the Web?

| by Jean-Jacques Dubray Follow 3 Followers on Mar 29, 2011. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Stu Charlon presented a set of slides at the WWW 2011 workshop on RESTful design titled "the Write Side of the Web". If the "read side" has been quite successful, "writing" information to the Web is not that easy, as some may have originally claimed at the height of the REST hype. The Write side it requires a fairly strong agreement, a.k.a coupling, between the client and the server in terms of semantics and error handling.

The Read Side The Write Side
  • GET
  • RDFa/Microformats
  • Browsing
  • Atom & RSS feeds
  • Search
  • Semantic Web
  • POST
  • AtomPub
  • Integration
  • Facebook Status
  • Media Sharing
  • e-Commerce

Stu explains that the growth in centralized services, which people increasingly call APIs and the need for system integration demand a better write side. Many so called RESTful design are diverging because there is not a commonly agreed way to handle the write side:

REST is not CRUD (Create, Read, Update, Delete), neither is HTTP. Post does not map directly to 'create' and CRUD itself leads to complexity at scale

CRUD actually requires a strong out-of-band agreement on validation rules and exception handling, in particular when it comes to CRUDing a series of states with specific transitions between them. In that case, the client needs to understand the server side state machine, at least partially. In his presentation, Stu details an Hypermedia-based programming model where the client "is an agent acting in an information space". He suggests tha client be:

Goal Directed
Has an hypermedia workspace
Sense to "pick up on effects"

People are only starting to discover the "Write side" and looking at most APIs these days, nobody is really taking the time to check if they are designing these APIs in a RESTful way. RESTfulie for instance is offering some interesting concepts on the server, in line with Stu's proposal, but in any case the client, and the agreement between the client and the server remains a problem that has been grossly overlooked by the REST community.

Are you designing "write side" APIs? what is your take on it?

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you