[Owncloud] Fwd: Re: ownCloud API

[Thomas Müller]

and now to the ml as well ....

--- Original Nachricht ---
Betreff: Re: [Owncloud] ownCloud API
Von: Thomas Müller <thomas.mueller at tmit.eu>
An: "Michael Gapczynski" <mtgap at owncloud.com>
Datum: 28.06.2012 18:18


Am Donnerstag, dem 28.06.2012 um 17:57 schrieb Michael Gapczynski:
> On Thursday, June 28, 2012 05:29:09 PM Evert Pot wrote:
> > On Jun 28, 2012, at 5:17 PM, Michael Gapczynski wrote:
> > > There is no standard for a RESTful web API, but this does meet the general
> > > expectations. Not all REST APIs that I've encountered require you to
> > > communicate using XML, but some just use POST parameters. I think POST
> > > parameters are always easier than generating XML. Then again, I'm not
> > > quite
> > > sure what an 'exported' API is.
> > 
> > If you use POST parameters for any other purpose than creating new objects,
> > you cannot really call it a RESTful web api :) XML is certainly also not a
> > requirement, but you should send over the entire entity you're replacing
> > with PUT, or the entire entity you're creating with POST.
> > 
> > Developing a true REST api is definitely something you should look at
> > though. It's more up-front work, but it forces you to design the API really
> > well, which may result a much higher longevity.
> > 
> > Evert
> 
> Okay, I took a closer look at this IBM article [1] and I'll agree with you and 
> Klaas that it isn't quite a REST API.
> 
> I would like to point out that with this definition Twitter and Dropbox don't 
> have a true REST API, but are called REST APIs. I did use the Google Documents 
> List API for the Google Drive external storage and that appears to follow the 
> principles in the article. It was a little more difficult to use however in my 
> opinion.
> 
> Klaas & Bartek - Since you both will be the first users of this API with the 
> sync client and Android app what would you prefer for changing resources: POST 
> parameters, XML (or other language), or something different.
> 

To change a resource you need to PUT the entity.
In general the resource representation within the http body should be the same regardless of the operation (GET,PUT,POST,DELETE)

I would suggest to go for json, because it's known to be 'easier' to parse and consumes less network bandwidth.
@Klaas:
Does Qt have a json parser by now?
If now we need to fallback to xml

@Bartek:
Android by now supports xml - right?
I know from the very first version only json was supported.

Tom / DeepDiver

http://de.wikipedia.org/wiki/Representational_State_Transfer
http://en.wikipedia.org/wiki/Representational_State_Transfer
> 
> Michael
> 
> 
> [1] https://www.ibm.com/developerworks/webservices/library/ws-restful/
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud