[Owncloud] owncloud API design guidelines

[Alessandro Cosentino]

I suggest to do it similar to OCS
> http://freedesktop.org/wiki/Specifications/open-collaboration-services
> Disclaimer: This was done by me. ;-)
>

very interesting, I was looking for something of this kind. I'll have a
look at OCS.


> It would also be nice to make it similar to the Google Reader API so that
> application developers can easily support both.
>

I have been look at the other API that feed aggregators expose, but there
are problems with all of them. Google Reader API are first of all not
officially documented. Secondly, they don't support important functions,
such as batch request of modifying a list of items. This is important to
avoid opening too many HTTP requests. Also, afaik, there are not
well-developed clients interacting with Google Reader, so that wouldn't
help much. Dan Vratil and Frank Osterfeld are developing an akonadi
resource for Google Reader using libkgoogle, but it's still a work in
progress.
About Newsblur API (this time very well documented!), again Jakob cast
doubts on how well they are designed, in particular on how well HTTP verbs
are used.

Alessandro



>
> Cheers
> Frank
>
>
>
> On 30.03.2012, at 16:02, Alessandro Cosentino <cosenal at gmail.com> wrote:
>
> > Hi,
> > I am going to design a RESTful webAPI for the rss aggregator app (I
> know, I am talking about this app too much) and I was wondering if there
> are any API design guidelines that ownCloud apps should follow.
> > I couldn't find this information on the website, neither could I infer
> anything from going through the code.
> > Have ownCloud API design guidelines been specified yet?
> >
> > Best,
> > Alessandro
> > _______________________________________________
> > Owncloud mailing list
> > Owncloud at kde.org
> > https://mail.kde.org/mailman/listinfo/owncloud
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120330/c53f0466/attachment.html>