First up, after working with the API for a few hours, I really do like the implementation. It's very easy and logical to use.
My main questions are about Persistent Data; 1) I can't find any talk of limits to this space anywhere - can we get some kind of guidelines on what to expect here. It obviously isn't going to be unlimited and while it's presumably up to the containers, there must have been some discussion about this. We need to have some idea about this in order to even begin planning applications that can be built using this data. 2) Has anyone thought about concurrency? Is there some way we can get some atomic functions here? If I read some persistent data (say a counter) then perform some action (say increment it) and then write back the updated value, we have a fairly obvious race condition if someone else loads the page and is modifying the same data. (Here's an example counter implementation that I wrote that will exhibit this; http://thatsmymouse.com/counter.xml ). In the current implementation there's no way to hold any kind of lock, or perform any atomic function on the data. This makes persistent data essentially useless - even if the data can only be modified by the same user, we end up with a race condition if the user loads two pages at once. I think this needs to be addressed pretty quickly! Thanks and keep up the good work! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
