API wrapper best practices?

Ashley Hindmarsh ash+perl at best-scarper.co.uk
Tue Mar 26 12:14:38 GMT 2013

> Message: 4
> Date: Mon, 25 Mar 2013 01:04:28 +0000
> From: Sam Kington <sam at illuminated.co.uk>
> Subject: Re: API wrapper best practices?
> To: "London.pm Perl M\[ou\]ngers" <london.pm at london.pm.org>
> Message-ID: <10D48713-D33C-40F3-84E9-B28C52D40EB0 at illuminated.co.uk>
> Content-Type: text/plain; charset=iso-8859-1
> On 24 Mar 2013, at 13: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, and is closer to what Dave Hodg is after.
> People thought of that, and now we have SOAP. So be careful for what you
> wish for.

I was using SOAP::WSDL as it reached v2.0 (ca. 2007).

It features a complete wrapping of XML Schema data types, from which a Perl
wrapper (accessors etc) can be generated, although you have to live with
that minimalism (e.g. all arrays + containers - no mappings).
Just wonder if the XML Schema wrapping could be extracted for use with
RESTful APIs which have well-defined schemas (I guess I may have just


> Sam
> --
> Website: http://www.illuminated.co.uk/

More information about the london.pm mailing list