Thanks Attila, If I can, I would like to avoid using a shared or vanilla scope per request if this is even possible.
When: 1. An object is defined at the top of a scope, and 2. Is then instantiated using the "new" keyword in a function further down in the scope, and 3. Assigned to a local variable within that function.. Where is the instance attached? Will it be garbage collected? It appears that the instantiated object, even though assigned to a local variable within the function, does not have access to the local scope of the function. In other words, my guess is that the instance is actually instantiated within the global scope, and then referenced by the local variable. Could this pose a memory leak problem? _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
