On Sep 4, 2008, at 1:05 PM, John Wilson wrote:
> The fact that Javascript does not support threads considerably > simplifies the situation. Well, JS as such has no threading or other concurrency primitives, this much is true. But you can have a JS environment where a program accesses objects shared by multiple threads, i.e., with Rhino in JVM... You're right that a JS runtime in a browser would most likely be single threaded (at least, have a thread-per-document, where it still wouldn't have any shared state with another script instance that operates in a different document). Attila. > > > John Wilson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
