The URL: http://wiki.opensocial.org/index.php?title=OSAPI_Specification
On Mon, Mar 30, 2009 at 12:01 PM, Bob Evans <[email protected]> wrote: > Hi, > > I have updated the OS Lite spec doc to match the current > implementation (there is a follow on patch coming today with the > metadata-based discovery of service methods). > > Known issues: > > * requestCreateActivity and activities.create. It might be possible to > make all calls ui-interruptible, but this prevents batching, well, > it makes batching a lot stranger and more involved. For example, what > happens if I have a batch where 2 of 4 calls require UI interaction > with the user. It's do-able, but would require a lot more thought than > .9 allows, I think. My proposed solution keep requestX methods, and > discuss making all service calls ui-intermediable in the next version > spec discussion. > > * send vs execute vs call naming. I prefer execute, but if people want > a shorter name, then send seems good. Some have suggested call as a > name, but this is used in the language, so seems like a bad idea. > > * Rename osapi.makeRequest to osapi.http.get/post. To me, makeRequest > reflects the existing, underlying gadgets calls, but I could see > making it http. > > * osapi.ui namespace is weird, better suggestions? > > * Should we have a bucket of params for the requestX calls, or > positional params as it is now? Maybe all of this is obviated if we > make the requestX calls be jsonrpc calls. > > > Thanks, > Bob >
