I don't know enough about CouchDB to say if its a good solution, but
am I correct in thinking its another server to setup and wont run in
the same JVM as the Shindig instance ? (Looking at the svn it see c
code, and mention of mod_couch ... sounds like it needs apache httpd
to run ).
To make it really easy for someone to take a Shindig instance out of
the box, the approach that Jackrabbit took might be worth following.
They used a default DB of Derby, which didn't need any config, as it
will run embedded. This also allowed them to make the TCK run all its
tests inside maven without additional config.
This may all be small point, since I see that Abdera has a number of
other ColectionAdapters including iBatis, Hibernate and even JCR.
--------------
Another quick question.
With the REST api being implemented, is there any point in
implementing the Services (eg PeopleService) that exist in the
current code base against a DB backend .... or will they be
deprecated shortly (within 4 weeks)
Ian
On 15 Apr 2008, at 17:28, Jun Yang (杨骏) wrote:
On Tue, Apr 15, 2008 at 7:30 AM, Santiago Gala
<[EMAIL PROTECTED]>
wrote:
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.
Yes.
or
will Shindig be implementing a rest based server component, with DB
backend
The first version will come with good support for relational
databases, as
is the common case.
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.
Since the server is based on Abdera and Abdera already has an
adapter for
CouchDB, this should be easy.
Jun
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/ <http://memojo.com/%7Esgala/blog/>
