-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gerald reminded me that we had this discussion before (http://markmail.org/thread/atzynccews3jlsys). Assuming a shared DB between Rave and Shindig, how does new OpenSocial information get pushed into the DB?
Marlon On 9/14/11 11:25 AM, Franklin, Matthew B. wrote: >> -----Original Message----- >> From: Marlon Pierce [mailto:[email protected]] >> Sent: Thursday, September 08, 2011 3:25 PM >> To: [email protected] >> Subject: Re: people.create, update, and delete not implemented in rave- >> shindig? >> > This is a limitation the Shindig API for PersonService > (org.apache.shindig.social.opensocial.spi.PersonService). Matt > implemented the API's get methods in DefaultPersonService, but to > implement updatePerson requires a change to the Shindig interface. > >> I didn't see resolution on this issue. IMO, Rave-portal & rave-shindig >> should share the same database instance for the demo application and in >> minor deployments. Internally, we plan to do what we did with OSEC & Rave, >> which is to define a common person service that both applications pull from. > > > > How should we proceed? > > > Marlon > > > On 9/8/11 2:32 PM, Marlon Pierce wrote: >>>> We need a way to update the rave-shindig database from >>>> rave-portal--for example, when a new user is created. I assume >>>> this should be done through the OS API with rave-portal calling >>>> shindig via REST or RPC API. However, it looks like person.create, >>>> person.update, and person.delete are not implemented; person.get is >>>> working ok. >>>> >>>> Assuming I'm not making a simple mistake, what do we need to do to >>>> enable the additional person methods? >>>> >>>> >>>> ----------------- Here is what I do: I have the following json >>>> >>>> { "method" : "people.get", "params" : { "userId" : "canonical" } } >>>> >>>> that I invoke with >>>> >>>> curl -H "Content-Type: application/json" -X POST -d >>>> @json-person.txt http://localhost:8080/rpc >>>> >>>> This works ok. However, changing the method to person.create (or >>>> update or delete) returns the following error: >>>> >>>> {"error":{"message":"notImplemented: The method people.create is >>>> not implemented","code":501}} >>>> >>>> I realize I need to also create a authorization token and may have >>>> an improperly formed JSON, but I assume these would throw >>>> different errors if the service was implemented. >>>> >>>> I'm following >>>> http://opensocial-resources.googlecode.com/svn/spec/2.0/Social-API- > Server.xml#People-Service-Create >>>> >>>> >>>> >>>> Marlon -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOcM6tAAoJEEfVXEODPFIDKBIH/jx/rbHJoNYEhL2+0jjO2RjL xnB0gTaPfx2jqYebNhM9L4nWJ4hWDKJv9Ps5pXowkM89oOB+BiHfHVsWoIOHOHUG rZgqh/pry3yX7TLhjXGkjRx+uOBInxOoxY/rPpPaqqU5UnfzW3h6tIUkZrm72daT 7Op/d0jKQoX0Oqk88I5TDtLd/LeuJjYi9nJ85Hig8qukWMHpJs4n3U4286dHArjd V6kfUm/PF0QYWOHzrrIVuDwX3oeVkbUkzP7D+/ZxH7hFT2iRe17XwGRORaKFdhFJ nc/A/V7H7QeJXMoMKvZjRRvXlrokXIG1jqy5fqN57L69PfmF5HSLlIGxUYkwQeI= =QyMm -----END PGP SIGNATURE-----
