But they will help with the "untrusted foreign code" bit, not so?

frank

"Andreas Raab" <andreas.raab at gmx.de> wrote:

> None of the cited references will solve the original problem(s). They
> are related but they won't solve it. Managing memory limits alone would
> require *major* modifications of the VM.
>
> Cheers,
>    - Andreas
>
> Frank Shearar wrote:
> > "Michael van der Gulik" <squeakml at gulik.co.nz> wrote:
> >
> >> Hi Howard.
> >>
> >> I forgot to mention that the reason I'm doing this is to allow
untrusted
> >> foreign code to run in the same image as trusted code. Untrusted code
> >> must be carefully managed - it must not be able to consume large
amounts
> >> of memory, CPU or disk space to which it is not entitled. Untrusted
code
> >> / objects must not prevent trusted code from operating well.
> >
> > Have you looked at the (Tweak) Islands [1] work? Lex Spoon also did work
> > with the same name [2], IIRC. And there's the Squeak-E [3] stuff too.
> >
> > [1] http://tweak.impara.de/TECHNOLOGY/Whitepapers/Islands/
> > [2] http://minnow.cc.gatech.edu/squeak/2074
> > [3] http://www.erights.org/history/squeak-e.html
> >
> > frank
> >
> >
> >
>
>
>