Does anybody feel there are any large oversights or omissions?

I might replace the export_procedures sub with something more declarative. Also, it would be nice to *not* have to use base 'XMLMethod';. Something like:

package MyPackage; use strict; use warnings 'all'; # This would import rpc_method into the current namespace: use XMLMethod 'rpc_method'; # Declare a method as rpc-able: rpc_method( 'math.sum', \&API::Math::sum, [qw/ int int int /] ); # Or maybe: rpc_method name => 'math.sum', method => \&API::Math::sum, signature => [qw/ @int /]; rpc_method name => 'math.avg', method => \&API::Math::avg, signature => [qw/ @int /]; rpc_method name => 'string.join', method => \&join, signature => [qw/ @str /];

In reply to Re: XML-RPC API layout by jdrago_999
in thread XML-RPC API layout by kalium

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.