On 13 Feb., 17:03, Attila Szegedi <[EMAIL PROTECTED]> wrote: > In Rhino-in-Spring I have serialization logic that both stubs the > prototype scope and also stubs the function bodies of all > (interpreted) functions, whether loaded into the prototype scope or > otherwise. The starting point is: > > <http://rhinoinspring.svn.sourceforge.net/viewvc/rhinoinspring/trunk/r... > > > > and the code for mapping function bodies to stubs is found here: > > <http://rhinoinspring.svn.sourceforge.net/viewvc/rhinoinspring/trunk/r... > >, search for "createFunctionStubs"
I guess the second link was supposed to go to the ScriptStorage class? http://rhinoinspring.svn.sourceforge.net/viewvc/rhinoinspring/trunk/rhinoInSpring/src/java/org/szegedi/spring/web/jsflow/ScriptStorage.java?view=markup > There's also a facility for digital fingerprinting of function bodies, > which might or might not be necessary in your case - it is important > with continuations to detect that the function on continuation stack > changed (i.e. reloaded script), as it invalidates the return addresses > on the continuation call stack, so failing cleanly early is preferred > to failing nondeterministically because of returning to a no longer > valid instruction offset in the caller... Very interesting. Thanks a lot for the pointers and explanation! hannes > Attila. > _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
