Nick Ing-Simmons <[EMAIL PROTECTED]> writes: >Allowing untested / constrained perl code to be run on a web server >is a daft as letting C code run.
It would be impractical for web hosts to vet each and every perl script a user uploads to their account. >So perhaps we should build a new executable webperl.exe >which is really "safe". Maybe, but what are the chances? >A magic command line which which limits CPU time isn't going to >help if program is reckless in other ways - e.g. a blocked >process consumes no CPU at all. If it stops 99% of problems it'll be a vast improvement. There is always a way around every solution, but if the solution works well then it's a improvement. Lyle
