Thanks for the performance tuning tip, I will look into that some time. Though my server is not likely to be used heavily with high traffic. But performance checking it might be good for finding any potential memory or resource leaks or high CPU consumption, deadlocks. Otherwise, I don't really need to optimize the code for performance at this time.

I actually made this post in terms of code design improvements. Specifically 2 things. (1) whether some of the code could be written according to modern (and proper?) Perl standards and using better Perl modules, optimizing for standards (rather than performance). (2) for any suggestions on how to fix or tackle the open issues and todo items I've listed in the project.

FYI, the server is used to serve QA/automation test libraries written in Perl remotely (on different machine or even just localhost) over XML-RPC for integration/use by RobotFramework.org test automation framework, using it's remote library API specification (which utilizes XML-RPC). The details on how the server works and what it's use is can be found on the wiki page link I mention earlier and in the Robot Framework documentation. Functionally, it works for basic support, but there's a few areas that can be improved for it to be up to standards with the reference spec implementation (the Python remote server for same framework).