Revision: [Initial Draft Revision] Date: 01-2009 All files related to the Javascript Bundle will be packaged inside an archive. The archive must be in an unprotected ZIP format, excluding 64-bit extensions to the ZIP specification. Compression of the archive's contents is optional.
By themselves, the files contained inside the archive do not convey any deployment information other than to suggest that the files be made available in a dedicated directory on the deployment server. Relative paths inside the archive should be maintained when extracting the archive.
Deployment information will be stored in a meta-data file inside the archive. Valid archives must contain a file named META_DATA stored inside a directory named JS_DEPLOY. The contents of the META_DATA file must be in valid JSON notation. See the Meta-Data specification for more information.
SecurityWhile most deployment servers will maintain a certain level of control over the Javascript Bundles deployed, there are conditions under which a deployment server may wish to restrict the types of content that can be deployed. Thus a deployment server may optionally reject a Javascript Bundle through either whitelisting or blacklisting of file types. If a deployment server implements such a provision, it must reject the bundle at the time of upload. The following files must be accepted by all deployment servers implementing this spec:
|