At 02:28 AM 10/25/2001 +0200, Espen Harlinn wrote:
>Instead of thinking about multiple threads, one could think about multiple
>execution contexts. Each instance of an object must belong to one and only
>one execution context. Each execution context has an attached security
>context and a security manager.
One actually needs to think about both. Threads and execution contexts
aren't required to be related. You could have multiple threads in a single
execution context (though it works badly with high-level languages as we
found with perl 5's pthread model, but that's a separate issue) or multiple
execution contexts with a single thread, which is what happens when you
allow a process to create multiple interpreters.
Parrot will support the single-thread/multiple-interpreter and
multiple-thread/multiple-interpreter models. (Where there's a 1:1
relationship between those multiple threads and multiple interpreters)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
