Recently I experimented with using DOJO AMD JavaScript modules
<http://dojotoolkit.org/documentation/tutorials/1.9/modules/> , of which
the hierarchy of 'js' files were all bound to a particular resource
reference class.
AMD allows for asynchronous loading of javascript code.
*My question is whether or not the resource reference path can be versioned
instead of the actual resource? *So that my module loader doesn't have to
know the version of the files in it's hierarchy of modules, and it can still
get up to date versions.
For instance, this:
/wicket/resource/my.project.DojoResourceReference_[some version code
(date or hash)]/some_module.js
Instead of:
/wicket/resource/my.project.DojoResourceReference/some_module[some
version code (date or hash)].js
/BTW
My experiment was successful for an ArcGis map project, in which the all the
map code is in a separate project that is used by the web project. And the
dojo module loader is able to pull modules asynchronously, yet not versioned
resources./
<http://dojotoolkit.org/documentation/tutorials/1.9/modules/> , of which
the hierarchy of 'js' files were all bound to a particular resource
reference class.
AMD allows for asynchronous loading of javascript code.
*My question is whether or not the resource reference path can be versioned
instead of the actual resource? *So that my module loader doesn't have to
know the version of the files in it's hierarchy of modules, and it can still
get up to date versions.
For instance, this:
/wicket/resource/my.project.DojoResourceReference_[some version code
(date or hash)]/some_module.js
Instead of:
/wicket/resource/my.project.DojoResourceReference/some_module[some
version code (date or hash)].js
/BTW
My experiment was successful for an ArcGis map project, in which the all the
map code is in a separate project that is used by the web project. And the
dojo module loader is able to pull modules asynchronously, yet not versioned
resources./