El mar, 15-04-2008 a las 03:59 -0700, Kevin Brown escribió: > On Tue, Apr 15, 2008 at 2:54 AM, Ian Boston <[EMAIL PROTECTED]> wrote: > > > Is the intention with the rest based apis for opensocial in shindig to > > just provide the JS client libraries and leave the implementation of the > > server side of the api to the implementor. > > > > or > > > > will Shindig be implementing a rest based server component, with DB > > backend. >
I wonder if using a very simple CouchDB backend could make sense. CouchDB offers a DB with native json API and javascript running in the server, so at least propotype support for initial experiments. It looks a great tool for this, though for a prototype python + simplejson + some dictionaries can actually be a similar very simple framework. Or s/python/<your favorite dynamic language>/ :) > > RESTful APIs are in development now, though nothing has been committed yet. > See mail archives for discussion. I'd expect the first commit within the > next week or two at most. The RESTful spec was just finalized last week -- > we need a little time! :) > > Also, is there any intention to use POST on the rest URL's to do updates to > > social data where it makes sense... sorry if this has been mentioned > > already. > > > We'll do whatever the spec requires. > +1, ReST requires POST/PUT for non-idempotent request, and *updates* are always non-idempotent. Even if I'm not following the spec right now, I would be very surprised if the spec used GET for updates. But this, as Kevin said, belongs to the spec ground. -- Santiago Gala http://memojo.com/~sgala/blog/
