API wrapper best practices?

[Joel Bernstein]

On 24 March 2013 14:13, Ashley Hindmarsh <ash+perl at best-scarper.co.uk> wrote:
> I guess the holy grail is something that takes the API schema and builds
> the classes on-the-fly

I don't know about holy grails but there's SPORE [0] which lets you
describe RESTful APIs and automatically generate clients for them in
different languages. There's a Perl implementation [1][2] but also
implementations for Ruby, Python, JS, Node.js among others.

If Dave's use case involves an API which can be modelled as a SPORE
specification then it might suit him well - it handles the http client
and call semantics parts, handing back perl hashrefs of the returned
data.

/joel

[0]: https://github.com/SPORE/specifications/blob/master/spore_description.pod
[1]: https://metacpan.org/module/Net::HTTP::Spore
[2]: http://lumberjaph.net/misc/2010/09/17/spore.html