Re: Make eLauncherAuthor thread-safe [patch]

On Mar 10, 2010, at 8:49, Thomas Leonard wrote:

> There are three commits. The first adds a VatSeeder Java class, which
> can be passed to Vat.seed and evaluates its twine in privileged scope.
> This is needed because safeScope is not thread-safe, so it is never OK
> to pass an E object here (as eLauncherAuthor does). It also changes
> seedVatAuthor to use the new system:
>
>  http://gitorious.org/~tal-itinnov/repo-roscidus/it-innovation/commit/8240992d252cdf65311113a6fd910ad468c1e3c8

Why not use seedVatAuthor rather than adding any Java code? It was our  
intent that seedVatAuthor is a sufficiently safe mechanism. Does it  
fail to be?

-- 
Kevin Reid                                  <http://switchb.org/kpreid/>