Klaas, you have my support on the REST conformity. Doing REST right is harder than a simple AJAX API.
Am 28.06.2012 11:34 schrieb "Klaas Freitag" <[email protected]>: > > On 26.06.2012 17:17, Tom Needham wrote: >> >> On 26 Jun 2012, at 16:06, Michael Gapczynski wrote: >> >>> What we need is a REST API that can handle user authentication and ownCloud >>> instance to instance communication. My idea is that the API is defined by the >>> apps, in which they register actions and requests for the API to listen to. >>> The API will handle the authentication and pass on the actions and requests >>> back to the apps. To ensure a stable API, I believe that actions and requests >>> should be defined in appinfo/info.xml and registered when the app is enabled. In a real REST API authentication is handled by HTTP (and then via tokens). > I don't want to nitpick or start something big on this, however we should be aware of the fact that this is probably not a REST API, but rather an exported ownCloud API. +1 > I am not saying we should to do it this way, yet it makes a difference. And we should think once in a while if we're REST conform or not. Maybe calling 'it' the 'ownCloud Exported API' OCEA is also fine. > > Two other questions with your proposal: > - How do we do error handling? In REST we would use HTTP error codes, maybe with json/xml content. > - Can/do we need more complex parameters passed to the functions, like arrays at least? Maybe we can find a standard for this? Well ... shouldn't that be done with POST requests and xml/json payload? So long Jörn
_______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
