Skip to main content

Resource Oriented Architecture? Inconceivable!

I'm looking forward to the new RESTful Web Services book.  I recall a 'Web Services' conference session a couple of years back on where the presenter essentially declared that WS-* had 'won' the standards 'wars'.  He dismissed REST with a wave and an indulgent chuckle.  Inconceivable!

REST's most visible implementation -- the Web -- has clearly been insanely popular as a read-only space.  There are many books on how to put documents on the Web. There are very few (no?) books on how to apply the full REST style to distributed programming over HTTP (inconceivable?).  It's appropriate that RESTful Web Services starts with a manifesto:

We want to restore the World Wide Web to its rightful place as arespected architecture for distributed programming. We want to shiftthe focus of web service programming from an RPC-style architecturethat just happens to use HTTP as a transfer protocol, to a URI-basedarchitecture that uses the technologies of the web to their fullest.

Does this remind anyone else of the clifftop scene from The Princess Bride?
[Scene: At the top. Fezzik, Vizzini and Inigo are looking down at
the masked man climbing the cliff after Vizzini has cut the rope]

Fezzik: He's got very good arms.


Inigo: You keep using that word. I do not think it means
what you think it means. [pause] My God! He's

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

XAuth is a Lot Like Democracy

XAuth is a lot like democracy:  The worst form of user identity prefs, except for all those others that have been tried (apologies to Churchill).  I've just read Eran's rather overblown "XAuth - a Terrible, Horrible, No Good, Very Bad Idea", and I see that the same objections are being tossed around; I'm going to rebut them here to save time in the future.

Let's take this from the top.  XAuth is a proposal to let browsers remember that sites have registered themselves as a user's identity provider and let other sites know if the user has a session at that site.  In other words, it has the same information as proprietary solutions that already exist, except that it works across multiple identity providers.  It means that when you go to a new website, it doesn't have to ask you what your preferred services are, it can just look them up.  Note that this only tells the site that you have an account with Google or Yahoo or Facebook or Twitter, not what the…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.