874
edits
m (rewording) |
(added notes on memory tracking) |
||
Line 6: | Line 6: | ||
* They are a superset of the [[ServerJS/Modules/SecurableModules|SecurableModule]] standard. | * They are a superset of the [[ServerJS/Modules/SecurableModules|SecurableModule]] standard. | ||
* They can be loaded and unloaded multiple times throughout the lifetime of their containing application. | * They can be loaded and unloaded multiple times throughout the lifetime of their containing application (yes, leaks are an unfortunate possibility). | ||
* They have access to an <tt>onUnload()</tt> function that allows them to register callbacks to perform cleanup tasks when unloaded. | * They have access to an <tt>onUnload()</tt> function that allows them to register callbacks to perform cleanup tasks when unloaded. | ||
* They have full access to XPConnect's <tt>Components</tt> object, and all its sub-objects. | * They have full access to XPConnect's <tt>Components</tt> object, and all its sub-objects. | ||
Line 19: | Line 19: | ||
* A simple, straightforward mechanism for writing and executing test cases. | * A simple, straightforward mechanism for writing and executing test cases. | ||
* An easy-to-learn documentation system capable of producing beautiful documentation. | * An easy-to-learn documentation system capable of producing beautiful documentation. | ||
* A mechanism for tracking objects of interest belonging to the Chrome Booster to aid in memory profiling and leak detection. |
edits