API wrapper best practices?
ash+perl at best-scarper.co.uk
Sun Mar 24 13:13:54 GMT 2013
> Message: 1
> Date: Sun, 24 Mar 2013 09:59:37 +0000
> From: Dave Cross <dave at dave.org.uk>
> Subject: Re: API wrapper best practices?
> To: london.pm at london.pm.org
> Message-ID: <514ECE89.1070908 at dave.org.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> On 03/23/2013 08:50 PM, DAVID HODGKINSON wrote:
> > Are there any tutorial type docs for Moose Meta the way you used it or
> > which man page should I be able to work it out from?
> Perhaps a course...
Actually I was about to point at something Moose-y that exercises a public
API, such as DC's Net::Songkick.
I was playing with this last year, and it's nice, but you always feel that
you shouldn't need to roll your own classes.
I guess the holy grail is something that takes the API schema and builds
the classes on-the-fly, and is closer to what Dave Hodg is after.
More information about the london.pm