>A wrapper is in most cases some type of frontend..a frontend that takes requests and looks at it and executes somthing else based on that request
Well, a wrapper for a frontend would be a frontend.

>highly restricted ... enviroment ... not a good enough answer
It's not? Why? There are lots of servers that let people login free, with little verification, and then let users have a *nix shell of some sort. Well, a few anyway. They seem to manage fine. If they can do it, surely the legendary Perl Monks can also achieve the modest goal of benchmarking?

Doing the benchmarking by hand would be much less elegant. But, still quite useful and effective.

Paris Sinclair    |    4a75737420416e6f74686572
pariss@efn.org    |    205065726c204861636b6572
I wear my Geek Code on my finger.

Im not stating fact, but Id be suprised if these free servers dont get at least one lame attack per-day, intentinal or not. Plus you have to look at it like this: The primary role that those severs play is to let users use their system, perlmonk's primary role is to run an interactive website that allows people to share knowledge about a specific subject (perl), not to sit around and manage users. I think that acctually giving users shell accounts, is even worse then having a restricted enviroment for the execution of user-supplied code :).