ServerJS/Modules/SecurableModules: Difference between revisions

ServerJS/Modules/SecurableModules (view source)

142 bytes added , 6 March 2009

Added a clause to the introduction that explicates the relationship between this specification and module loaders.

171

edits

Revision as of 20:56, 4 March 2009 (view source) KrisKowal (talk \| contribs) (Removed mention of file system backends) ← Older edit		Revision as of 03:00, 6 March 2009 (view source) KrisKowal (talk \| contribs) (Added a clause to the introduction that explicates the relationship between this specification and module loaders.) Newer edit →
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. By implication, this specification defines the minimum features that a module system must provide in order to support interoperable modules.

	== Contract ==		== Contract ==