Re: Designing a good REST API, HATEOAS, etc
Re: Designing a good REST API, HATEOAS, etc
- Subject: Re: Designing a good REST API, HATEOAS, etc
- From: Pascal Robert <email@hidden>
- Date: Mon, 02 Apr 2012 14:12:04 -0400
For the fun of it, looks like the Google Docs API is also using ATOM.
> Hi James,
>
> I'm still planning at looking at this, but sadly I didn't have the time. Also, every time I ask where are the HATEOAS clients, the only reply I get is that people only use it for "inside apps". The only time I saw something similar to HATEOAS that is actually used and public is the CMIS standard.
>
> I still think it's doable to build responses in HATEOAS by adding a reader and a writer to ERRest (.atom for the extension) but beside building it for learning, I don't see a need unless intelligent clients can use it.
>
>> I am curious to know whether anyone has used ERRest to build a REST API that fulfills the HATEOAS part [1](hypermedia as the engine of application state) of the REST architectural style. Any real world examples that are publicly available? I am guessing that most API implementations largely miss this and force clients to construct URLs, which leads to strong coupling. I am not keen to get into an academic debate at the expensive of actually building something but it seems like a good selling point for the ERRest framework if it can in some way guide developers to build true hypermedia APIs that clients can 'discover' and that encourage loosely coupled clients.
>>
>> I see that Pascal mentioned the possibility of a future presentation on HATEOAS and Atom in his WOWODC 2011 presentation on "Designing a Good Rest Service" [2].
>>
>> I think perhaps the ERRest json-schema support and the HTML routing are useful for this but the wiring up of the hypermedia links and forms would not be handled by the framework.
>>
>> If anyone is interested there are a couple of interesting talks on this, including one [3] where the content-type of the responses is XHTML and clients use xpath (it does make sense although I don't think I would go that way) and also another approach from Ian Robinson [4], who is using XML, Atom and XForms.
>>
>> I am interested in opinions from the WOCommunity about real world REST and HATEOAS.
>>
>> --
>> James
>>
>> [1] http://en.wikipedia.org/wiki/HATEOAS
>> [2] http://www.slideshare.net/wocommunity/er-rest-designinggoodapi (the slides don't display in the browser, only the download link works)
>> [3] Jon Moore from Comcast on "Hypermedia APIs" - https://vimeo.com/20781278
>> [4] Ian Robinson on "Hydras and Hypermedia" - https://vimeo.com/28541275
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden