Hey Guys,

Finishing the last bits for the socialdata work on the PHP side, and only a tiny bit away from a fully functioning implementation.

However part of the test i'm using (http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml ) requires data to be written as well to get a green across the board compliance status.

Now on the java side this has been done by keeping the person app data in memory, which of course means when jetty is restarted its lost, which is probably what you want in a sample container kind of situation. However in PHP land i'm stuck in a multi process model with no persistent shared memory (unless i would want to add arbitrary extra layers to the whole thing, which i don't).

So instead i opted for actually writing the new data (or replacing if it existed) to the state file (state-basicfriendlist.xml), this way any consequent reads of the data can actually succeed, and i get green fields across the board in the compliance test :)

It could well be possible that some people might be playing with both the PHP and Java versions and examples / samplecontainer etc, and i'm lacking the insight to know if this could somehow affect the Java side of things. Presumably not, especially because at some point of the future this code will be scrapped and replaced with the REST interface but it felt better to double check :)

        -- Chris

Reply via email to