Reasons why Perl might not be an ideal choice

While Perl is a very versatile language, it is not perfect for all tasks. First of all, the program must be compiled every time it is invoked. While the Perl compiler is very efficient, being able to compile very large programs in fractions of a second, it is a step that must be repeated many times, maybe innecesarily. This makes the wrapper not suitable to be run as an inetd process if it will be called at least once every five seconds.

Perl is also not very conservative in RAM. Even the simplest program will take an absolute minimum of 1.5 Megabytes. This makes it impractical to run many instances of the wrapper as standalone processes on a limited machine. The author would advises having at least 5MB of available physical RAM for each wrapper class. ProtoWrap, in its present form, is not made to endure heavy load situations - in fact, a DoS attack can easily stop the machine from responding to requests . It is however preferable for a computer to get trapped in a DoS attack, which poses no real danger to the configuration and data stored in the server, than to suffer direct attacks to the real daemons.