I built a custom XML-RPC server in Perl that "supposedly" serves any given Perl code module/class whose structure conforms to some compatible specifications, and the server serves it dynamically at startup via reflection/introspection. It's built out of code snippets found on this site along with a Wikipedia page, with my glue code to mash everything together. It's also modeled (in terms of design) after my server implementations for other languages (.NET, Java). For this post, I'm asking for feedback from Perl community what improvements, if any, I could make to the server. Suggestions on how to implement bug fixes for the open issues of the server, and if there is a more optimal approach to reflection for executing a Perl class method or listing out the class methods information. As the material I based it on and Perl language itself has more than one way to do things.

In terms of optimal code reflection, I'm looking for optimizing or solution where it can satisfy a majority of Perl code or modules, w/ no or minimal changes or wrappers to the Perl code being reflected in most cases.

I guess this is kind of a broad question post, but in a nutshell just wanted feedback for improvements to my server. Don't know where else is good place to seek feedback for Perl.

http://code.google.com/p/plrobotremoteserver/source/browse/#svn%2Ftrunk

http://code.google.com/p/plrobotremoteserver/wiki/UsageInfo

http://code.google.com/p/plrobotremoteserver/issues/list

and the server is built against the remote library interface spec for RobotFramework

http://code.google.com/p/robotframework/wiki/RemoteLibrary

with the reference implementation (to the spec) being in Python.

In reply to Seeking design improvements for Perl code library remote server by daluu

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.