Resourced. This whole ROA vs SOA debate, where are we going with that?
You know, these services don’t come out of thin air and certainly don’t connect themselves, so on any given day you need to decide which technologies to use to make that happen. It’s SOAP vs REST boxing match brought to you by the S.O.A Federation. I placed my bets, but I’m watching closely because it’s still a fair fight.
I also get resource thinking, which is something entirely different. Everything is a resource, resources are linked, and besides the few servers in my back yard, I can reach and touch resources across the world. Cool. Magnificent. Awe. Brave new world. Also a staged fight, we already know who takes the first round by a KO, but still selling tickets for this match.
But now I’m hearing on the PA that “people who SOA do not REST”. Darn. I really thought REST stood a chance in this fight. I may cry a bit.
Then we’re off to commercials, where I learn that “if you or someone you know has a chronic resource pain, ask your doctor about prescription R.E.S.T,” and I’m wondering to myself, what is a chronic resource pain? What are the symptoms? How do you know you have it?
Where was I going with this? Oh yeah. I know cheerleaders need some letters to shout out, but before we get to that, can we take a quiet moment to reflect and articulate what problem we’re trying to solve. In one sentence or less:
I _____________________________ and I used resources for that.
Also. OAuth 1.0 final draft (that was fast!)
Simplified. OpenID site redesigned with a much improved ‘where do I get one?‘ page. The explanation is still geek-oriented, but definitely a step in the right direction. (Via Simon Willison)
Guaranteed. Amazon S3 Service Level Agreement. (Also via Simon Willison)
