Hi Ben, On 12 Feb., 21:21, [EMAIL PROTECTED] wrote: > > I've instrumented my ScriptableOutputStream to log all of the objects > it is asked to replace, and from this log it seems clear that the > objects in the global scope (compiled functions mostly) to which my > session is maintaining references are still being offered for > serialization even though their parent scope is stubbed with the > proxy. >
I found a possible explanation for what you're describing. If you serialize a function defined in a script file, the whole compiled script will be serialized as well. So if you have both your local/per session code and the global code in the same script file, breaking the code up in two or more files may help. Maybe this fixes it, and I'm glad I also learned something new along the way :-) Hannes _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
