So says Roy Fielding, the author of the paper that defined REpresentational State Transfer (REST). And the same goes for the OpenSocial REST API, which is the basis for the SocialSite REST APIs. Here's part of his comment about OpenSocial:
Roy Fielding: The OpenSocial RESTful protocol is not RESTful. It could be made so with some relatively small changes, but right now it is just wrapping RPC results in common Web media types.
There are lots of advantages to being RESTful and we certainly want both the OpenSocial and the SocialSite REST APIs to live up to their names, so I'm glad to hear the changes are "relatively small." Now we just need to figure out what those changes are. I asked Roy to elaborate and I also started a
thread (Google Groups login required) on the topic in the OpenSocial spec discussion group.
SocialSite REST API not so RESTful
So says Roy Fielding, the author of the paper that defined REpresentational State Transfer (REST). And the same goes for the OpenSocial REST API, which is the basis for the SocialSite REST APIs. Here's part of his comment about OpenSocial:
There are lots of advantages to being RESTful and we certainly want both the OpenSocial and the SocialSite REST APIs to live up to their names, so I'm glad to hear the changes are "relatively small." Now we just need to figure out what those changes are. I asked Roy to elaborate and I also started a thread (Google Groups login required) on the topic in the OpenSocial spec discussion group.Posted on: Oct 21, 2008
Posted by: davejohnson
Category: APIs and specs
Permanent link to this entry