Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 2.1, Advanced Components Environment (ACE)
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration
Description
In ICEfaces 2.0.x the mandatoryResourceConfiguration parameter defaults to null, which results in all JavaScript and CSS resources for all components in the application being pre-loaded on each initial page load. This allows components to function correctly even if they are later added to the page dynamically during user interaction.
Unfortunately, it also bloats each page load substantially (2+ MBs) and usually unnecessarily as most components are already on the page when it loads, and not added dynamically.
To improve the out-of-the-box ICEfaces performance as it relates to page sizes and load times, we will change the default for mandatoryResourceConfiguration to 'none. This will result in no component resources being preloaded (only the resources for components on the page at initial load time will be loaded), resulting in an optimal resource load situation.
This also means that any applications that are introducing ace components to the page dynamically (there are added to the page as part of a subsequent ajax page update and not during the initial page load) will now need to configure the mandatoryResourceConfiguration parameter (or preferably, the <icecore:config mandatoryResource=""> tag which can be specified per-view) in order to continue to function correctly.
Unfortunately, it also bloats each page load substantially (2+ MBs) and usually unnecessarily as most components are already on the page when it loads, and not added dynamically.
To improve the out-of-the-box ICEfaces performance as it relates to page sizes and load times, we will change the default for mandatoryResourceConfiguration to 'none. This will result in no component resources being preloaded (only the resources for components on the page at initial load time will be loaded), resulting in an optimal resource load situation.
This also means that any applications that are introducing ace components to the page dynamically (there are added to the page as part of a subsequent ajax page update and not during the initial page load) will now need to configure the mandatoryResourceConfiguration parameter (or preferably, the <icecore:config mandatoryResource=""> tag which can be specified per-view) in order to continue to function correctly.
Issue Links
- blocks
-
ICE-6951 Reduce required resource loading on initial page loads due to mandatoryResource default settings
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Fix Version/s | 2.1-Beta [ 10291 ] | |
Affects | [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration] | |
Assignee Priority | P1 | |
Affects Version/s | 2.0.2 [ 10273 ] | |
Assignee | Ken Fyten [ ken.fyten ] |
Summary | Change default value for 'mandatoryResourceConfiguration' from 'all to 'none' | Change default value for 'mandatoryResourceConfiguration' from null to 'none' |
Salesforce Case | [] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Assignee Priority | P1 | |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Assignee Priority | P2 | |
Assignee | Ken Fyten [ ken.fyten ] | Ted Goddard [ ted.goddard ] |
Assignee | Ted Goddard [ ted.goddard ] | Ken Fyten [ ken.fyten ] |
Salesforce Case | [] | |
Assignee | Ken Fyten [ ken.fyten ] | Mark Collette [ mark.collette ] |
Salesforce Case | [] | |
Assignee Priority | P2 | P1 |
Assignee | Mark Collette [ mark.collette ] | Ted Goddard [ ted.goddard ] |
Comment |
[ Or just revert this change to the default and add "none" to whatever sample application was of concern. ] |
Comment | [ I agree with Ted, we added this feature to make post-backs work by default, and allow for performance tuning from there. This is in line with DOM differencing making page updates work by default, and f:ajax tuning it if necessary. I'm not sure we want to migrate mandatoryResourceConfiguration to a mode of the post-backs being broken by default, and needing to be enabled to function. ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Assignee Priority | P1 | |
Resolution | Fixed [ 1 ] |
Salesforce Case | [] | |
Fix Version/s | 2.1 [ 10241 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Assignee Priority | P1 |
Salesforce Case | [] | |
Assignee | Ted Goddard [ ted.goddard ] | Mircea Toma [ mircea.toma ] |
Assignee | Mircea Toma [ mircea.toma ] | Ted Goddard [ ted.goddard ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Salesforce Case | [] | |
Fix Version/s | 2.1-Beta2 [ 10294 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |