Stop Writing REST API Clients
ttezel.github.com
Stop Writing REST API Clients
1–10 of 137 posts
Re: Stop Writing REST API Clients
#2Nice idea!
Re: Stop Writing REST API Clients
#3[deleted]
Re: Stop Writing REST API Clients
#4[deleted]
[deleted]
Re: Stop Writing REST API Clients
#5This is essentially trying to solve the same problem as Swagger. Swagger is "a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services" [1]. Check out the spec on GitHub here [2].
Re: Stop Writing REST API Clients
#6While this has some benefits, it seems like a slippery slope leading back to SOAP.
Re: Stop Writing REST API Clients
#7[deleted]
Re: Stop Writing REST API Clients
#8Substitute "XML" for "JSON" and we've now come full circle.
The point about REST is that it is self-describing. And ideally should be using the same URIs as the version people clicking around in Firefox or Chrome see. The API is just the XML or JSON or whatever is flavour of the week version of the HTML version.
(Or we could use embedded data—microformats, microdata, RDFa—and get rid of that distinction.)
Re: Stop Writing REST API Clients
#9swagger (http://developers.helloreverb.com/swagger/) has been doing whats proposed here. By describing your APIs with swagger-spec you get a beautifully documented APIs, code generation of client libraries and some more stuff: https://github.com/wordnik/swagger-core/wiki/Downloads
Re: Stop Writing REST API Clients
#10While this has some benefits, it seems like a slippery slope leading back to SOAP.
Exactly. But to be precise, REST would be the equivalent of SOAP and the format described in this post would be equivalent to WSDL [1].
And then, we'll need a central location to store all of these API descriptors and UDDI [2] will be back with a vengeance.
[2] http://en.wikipedia.org/wiki/Universal_Description_Discovery...