A typical TRIRIGA UX application will initially load hundreds of resource files which translate to the same number of HTTP requests from the server to the browser. This remains true in the succeeding requests of these resources even if they are already cached by the browser. The browser still makes the same number of HTTP requests to the server then waits for the server response to either load it from the cache or from the latest version from the server. This great number of HTTP requests is costly and can affect the performance of your application. One way of cutting down this cost is to concatenate these web resources into a single file through the Vulcanize build tool created by the Google Polymer team.
The TRIRIGA team developed a tool called tri-vulcanize that specifically vulcanizes TRIRIGA UX component files. It pulls the component files from the TRIRIGA server based on the given view to vulcanize, then uses the Google Vulcanize build tool to concatenate these files into a single file.
- Upgrade TRIRIGA Platform version 3.5.2 to be able to vulcanize UX applications.
- Upgrade TRIRIGA Application version 10.5.2 to get the vulcanized Perceptive applications.
- Download the tools here.
- Setup the UX metadata for customized and new UX applications.
When do I vulcanize my UX Application?
You will need to vulcanize your UX application whenever there are changes to your view files or platform component files. These usually happen when a developer has updated your view files or from application OMs and platform upgrades. It is best to re-vulcanize your UX applications when any of these changes occurred, even if you are not sure that there were UX component and application files getting updated in the upgrade…