171
edits
ServerJS/Modules/SecurableModules: Difference between revisions
ServerJS/Modules/SecurableModules (view source)
Revision as of 22:47, 4 February 2009
, 4 February 2009→Securable Modules
(New page: == Securable Modules == This specification addresses how modules should be written in order to be interoperable among a class of module systems that can be both client and server side, se...) |
|||
| Line 1: | Line 1: | ||
This specification addresses how modules should be written in order to be interoperable among a class of module systems that can be both client and server side, secure or insecure, implemented today or supported by future systems with syntax extensions. These modules are offered privacy of their top scope, facility for importing singleton objects from other modules, and exporting their own API. | This specification addresses how modules should be written in order to be interoperable among a class of module systems that can be both client and server side, secure or insecure, implemented today or supported by future systems with syntax extensions. These modules are offered privacy of their top scope, facility for importing singleton objects from other modules, and exporting their own API. | ||
| Line 18: | Line 16: | ||
# Whether a PATH is supported by the module loader for resolving module identifiers. | # Whether a PATH is supported by the module loader for resolving module identifiers. | ||
=== Sample Code | == Prototype == | ||
A prototype for a client-side module loader that supports modules that conform to this specification using PATH relative URL's or module relative URL's without making security guarantees is partially complete in the [[http://code.google.com/p/chironjs/source/browse/branch/safe/src/modules.js "safe" branch of modules.js]]. | |||
== Sample Code == | |||
// ================================================== | // ================================================== | ||