How I learned to stop worrying and love REST
mikemayo.org
How I learned to stop worrying and love REST
1–10 of 38 posts
Re: How I learned to stop worrying and love REST
#2Disclaimer: I do not want to steal the author's page views, but I could hardly read this article, due to the white shadow in the Text. Here is a more readable view: http://rdit.in/5c
Re: How I learned to stop worrying and love REST
#3Disclaimer: I do not want to steal the author's page views, but I could hardly read this article, due to the white shadow in the Text. Here is a more readable view: http://rdit.in/5c
Frankly that shadow has always bothered me too. I've changed it up now, hopefully that's a little easier on the eyes.
Re: How I learned to stop worrying and love REST
#4Disclaimer: I do not want to steal the author's page views, but I could hardly read this article, due to the white shadow in the Text. Here is a more readable view: http://rdit.in/5c
In Chrome I do right-click, inspect element. Then I CSS the shadow away :)
Re: How I learned to stop worrying and love REST
#5This is probably my number one criticism of most "REST" APIs out there - they are horribly non self-documenting, and the effort required to make them self-documenting is really fairly trivial:
1. Ensure that you have a URI to the resource in question every single time you reference an ID somewhere (in collections, when referencing resources from another resource)
2. Make the root of your application document all the collections available and their respective URIs.
3. Include paging URIs as mentioned in the article.
4. If a resource has nested collections, include URIs to them in your JSON representation of the resource.
Boom! You now have a REST API better than 99% of what's on the web today.
Re: How I learned to stop worrying and love REST
#6I hate when people try tell me REST isnt the way to go. I guess if you're an out-dated organization with a lot of time (and money) on your hands, you could stuff around with something else...but why would you in this world as a startup do anything else?
Nice article, i think the world needs a very basic "this is how you use REST" bullet point style blog post somewhere. This lesson would be 1 of those bullet points if i were writing it.
Re: How I learned to stop worrying and love REST
#7This is probably my number one criticism of most "REST" APIs out there - they are horribly non self-documenting, and the effort required to make them self-documenting is really fairly trivial: 1. Ensure that you have a URI to the resource in question every single time you reference an ID somewhere (in collections, when referencing resources from another resource) 2. Make the root of your application document all the…
and this is what i was talking about!
Re: How I learned to stop worrying and love REST
#8This is probably my number one criticism of most "REST" APIs out there - they are horribly non self-documenting, and the effort required to make them self-documenting is really fairly trivial: 1. Ensure that you have a URI to the resource in question every single time you reference an ID somewhere (in collections, when referencing resources from another resource) 2. Make the root of your application document all the…
and this is what i was talking about!
[deleted]
Re: How I learned to stop worrying and love REST
#9good to see a hometown guy on the frontpage of HN ... I feel proud (for once) to be from Louisiana :P