Your REST API should come with a client

Re:Your REST API should come with a client by svedlin on Monday April 28, 2014 @03:58AM (#7658747)

The Google APIs Client Generator is an awesome tool that automates this process. It takes a service description and generates a complete client library:

https://code.google.com/p/google-apis-client-generator/

The service is defined in a platform-neutral discovery document, which can be used by any provider:

https://developers.google.com/discovery/v1/reference/apis

There are generators for Python, Java, .NET, Objective-C, PHP, Go, GWT, Node.js, Ruby, and others.

[ Parent | on HN ]

Re:Your REST API should come with a client by quotemstr on Monday April 28, 2014 @04:26AM (#7658823)

> The Google APIs Client Generator is an awesome tool that automates this process. It takes a service description and generates a complete client library

So we've gone full circle and arrived back at SOAP. Why didn't we just keep using SOAP in the first place?

[ Parent | on HN ]

Re:Your REST API should come with a client by jordanthoms on Monday April 28, 2014 @04:37AM (#7658855)

Well, at least the underlying API is much simpler - you can do things manually if necessary. Trying to talk to WCF SOAP services from Ruby has been really painful - none of the SOAP libraries actually work with the Microsoft stuff, and it's so overcomplicated that making requests manually is a pain.

[ Parent | on HN ]

Re:Your REST API should come with a client by LunaSea on Monday April 28, 2014 @08:05AM (#7659376)

Because SOAP is an unnecessary overhead and complication. It also kills performance.

[ Parent | on HN ]

Re:Your REST API should come with a client by bluefinity on Monday April 28, 2014 @11:15AM (#7660464)

Because everybody's SOAP implementation is subtly different, leading to bugs/pain/things not working.

[ Parent | on HN ]