Let's pretend you have a web application that supports user scripts.
As soon as you allow users access to other peoples scripts, you may want to make sure people don't abuse it. so you need either to
a) filter js so that no endless loops/function definition(and therefore endless recursions) and unwanted API calls appear
b) Have a safe language compiled to JS on the server
c) Have a safe language interpreted at the client on top of JS
d) ???
What are the options, gee?
>>55511430
Bumpedidump
Do your own homework you stupid faggot.
>>55511430
Filter is not an idea...safe language might be difficult to implement bit you can interpret it on the fly with JavaScript itself...or you can define a "secure" api
You could define permissions to access your resources, and limited quotas to use them. That way no matter what your users do, they won't exceed over the limit they have assigned to them.
>>55512402
>implying this is a OR THIS BIRD STABS YOU bread
>>55512408
Thanks, that is the only answer that goes even remotely in to the right direction. Now, I don't want to reinvent the wheel, so: Does something like this exist already?