Stop Writing REST API Clients • Hacker News Board

Re: Stop Writing REST API Clients

#31

Post by shurcooL » Sun, Feb 24, 2013, 4:33 PM UTC

TelmoMenezes wrote: post #24

Am I the only one who doesn't like receiving direct orders from article titles?

Would it help if he prefixed it with "In this article, I argue for why I believe that you should"?

Re: Stop Writing REST API Clients

#32

Post by ayushgta » Sun, Feb 24, 2013, 4:35 PM UTC

feralmoan wrote: post #25

Isn't this what http://json-schema.org aims to provide? Or am I missing something. It's a solid spec.

Json Schema is pretty good at describing data coming through JSON. But describing (REST) APIs requires more. For example a standard way to describe API endpoints with parameters and response types, errors, related models, default/allowable values etc. This was what the OP was referring to and this is what Swagger is trying to do. The Swagger Spec is here with some more details on whats required in addition to JSON Schema to document APIs: https://github.com/wordnik/swagger-core/wiki/API-Declaration Incidentally model/data specifications in swagger spec does map closely with json schema.

Re: Stop Writing REST API Clients

#33

Post by taude » Sun, Feb 24, 2013, 4:35 PM UTC

Hmmm....JSON documents (jsonSpec) describing the restful services is the new WSDL, feels like 2002 all over again.

I think too many people consume REST APIs in different manners, utilizing different data in unique relations. This is the beauty of it.

Re: Stop Writing REST API Clients

#34

Post by Goopplesoft » Sun, Feb 24, 2013, 4:35 PM UTC

TelmoMenezes wrote: post #24

Am I the only one who doesn't like receiving direct orders from article titles?

I was thinking about this yesterday, but its seems like HN likes that kinda thing. Lots of frontpage article are direct orders from blogs with who knows what credibility.

Re: Stop Writing REST API Clients

#35

Post by TallboyOne » Sun, Feb 24, 2013, 4:36 PM UTC

TelmoMenezes wrote: post #24

Am I the only one who doesn't like receiving direct orders from article titles?

I was just thinking that, I hate article titles that are phrased exactly as a command and it's merely a blog post that wants to change an entire body of thought that's well founded.

Re: Stop Writing REST API Clients

#36

Post by taude » Sun, Feb 24, 2013, 4:36 PM UTC

taude wrote: post #33

Hmmm....JSON documents (jsonSpec) describing the restful services is the new WSDL, feels like 2002 all over again. I think too many people consume REST APIs in different manners, utilizing different data in unique relations. This is the beauty of it.

whoops, just saw other comments on the whole, feels like WSDL all over again.

Re: Stop Writing REST API Clients

#37

Post by ayushgta » Sun, Feb 24, 2013, 4:37 PM UTC

eintr wrote: post #26

Yeah, let's do CORBA once again. No thanks.

Oh Shit! Common Object Request Broker Architecture!! I'd thought all fellow humans from that era had been killed and buried :)

Re: Stop Writing REST API Clients

#38

Post by mattdeboard » Sun, Feb 24, 2013, 4:39 PM UTC

shurcooL wrote: post #31

TelmoMenezes wrote: post #24

Am I the only one who doesn't like receiving direct orders from article titles?

Would it help if he prefixed it with "In this article, I argue for why I believe that you should"?

Yes. Assuming guru voice just makes you sound like a blowhard.

Re: Stop Writing REST API Clients

#39

Post by Goranek » Sun, Feb 24, 2013, 4:39 PM UTC

shurcooL wrote: post #31

TelmoMenezes wrote: post #24

Am I the only one who doesn't like receiving direct orders from article titles?

Would it help if he prefixed it with "In this article, I argue for why I believe that you should"?

Yes! :)

Re: Stop Writing REST API Clients

#40

Post by spo81rty » Sun, Feb 24, 2013, 4:39 PM UTC

We need WSDL for REST to solve this problem. Then we could code generate clients.