Publication Date: 2014-May-09
The IP.com Prior Art Database
Page 01 of 8
Other popular js framework may have similar methods to do this work.
But this is not enough, especially in the initial loading time, for those rich client web applications with large quantity of js modules. Let's take a typical transportation management web application as example, even after js build, the initial loading response time will be over 10s in an average quality of WAN, and most of the time is spent on loading the compressed js file with a footprint about 5-10MB. The response time is still not meet the basic requirement, for a good user experience.
One way to improve it, is to divide the one large compressed js files into several and provide a on-demand loading for each. As a Prior Art, some js build tools have the capability to support js file combination into several rather than one js file.
However developers should specify complicated profiles, and it fully depends on the developers' understanding of page structure, js module(file) structure and their dependencies, which is very hard to realize. At the same time the granularity is not fine enough to do it in this way.
There are some automatic builder that can calculate js dependency-tree, and run some optimization in shrinking code. But these dependencies are not related to specify web-page, therefore can not optimize dire...