[mashup-dev] Javascript Function Scheduler Updates

Tyrell Perera tyrell at wso2.com
Mon Feb 4 08:20:59 PST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FYI:

While resolving MASHUP-630 (https://wso2.org/jira/browse/MASHUP-630)
reported by Jonathan, I came across a few architectural flows in the
previous javascript function calling mechanism. So I re-wrote it.

The periodic javascript scheduler is now identical to the Javascript
message receiver in functionality as far as executing javascript code is
concerned.

This means that before executing any scheduled javascript function or
code fragment inside a service js file, it will load the relevant script
includes along with the parent service javascript file.

This approach ensures that all the necessary dependencies are in scope
before the scheduled function or block of js code is called. This also
guarantees the availability of a valid rhino context (which was the bug
behind MASHUP-630).

Note: No API changes for setInterval() or clearInterval(), just an
internal architecture upgrade :)

Cheers,
Tyrell


- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell at wso2.com; cell: +94 77 302 2505

"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHpztrehFdPcgGx7oRAuJPAJ0aN9cRlyH+lqTHH9fn0SpQdxzIawCcCxsB
hzlXr41gx1GhBfunopuFoKk=
=q8C4
-----END PGP SIGNATURE-----



More information about the Mashup-dev mailing list