Re: How much REST should your Web API get?
Jérôme Louvel <[email protected]> Fri, 3 May 2013 19:39:04 +0200
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <CAOsY8mTdaVyjfnhHtWrkt0ej38Cn8=vKHCkHXy3fcwZoLCQOKw@mail.gmail.com> |
Yes, this is another great post from Kin. However this approach doesn't make sense in a pure REST world when there isn't place for such out-of-band definition of the interface (uniform interface). Another reason to think about those aspects in a separate architecture style. Best regards, Jerome 2013/5/3 Mike Schinkel <[email protected]> > On May 3, 2013, at 8:04 AM, Jérôme Louvel <[email protected]> wrote: > > Regarding media types, their power lies in their standardization. Having > a separate one for each application isn't that useful, and ends up with the > media type being used in a generic JSON/XML way or abstractes away in a > programming client SDK. > > Exactly. > > Given Jan's "Not gonna happen" comment[2] related to standardization of > media types, I found this blog post[1] from Kin Lane posted yesterday oddly > well-timed. :) > > -Mike > > [1] > http://www.apievangelist.com/2013/05/02/startups-need-to-work-together-on-api-definitions/ > [2] http://tech.groups.yahoo.com/group/rest-discuss/message/19384