ICEfaces
  1. ICEfaces
  2. ICE-6655

Add parameter to make hidden history iframe inclusion configurable

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.8.2-EE-GA_P02
          • Fix Version/s: EE-1.8.2.GA_P03
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            -
          • Affects:
            Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

            Description

            The user has a scalability concern and would like to optimize portal application load performance by removing the hidden blank iframe that is used to support back/forward browser history. For example, if 30000 users at 3000 different locations open a page with 10 ICEfaces portlets, the addition of 300,000 potentially unneeded iframes may degrade performance. Removing this iframe should not affect portlet functionality since navigation is not as expected in a portal environment.

              Activity

              Ascending order - Click to sort in descending order
              Tyler Johnson created issue -
              Tyler Johnson made changes -
              Field Original Value New Value
              Salesforce Case [5007000000F7jdu]
              Tyler Johnson made changes -
              Description The user has a scalability concern and would like to optimize portal application load performance by removing the hidden iframe that is used to support back/forward browser history. For example, if 30000 users at 3000 different locations open a page with 10 ICEfaces portlets, the addition of 300,000 potentially unneeded iframes may degrade performance. Removing this iframe should not affect portlet functionality since navigation is not as expected in a portal environment.
              		The user has a scalability concern and would like to optimize portal application load performance by removing the hidden blank iframe that is used to support back/forward browser history. For example, if 30000 users at 3000 different locations open a page with 10 ICEfaces portlets, the addition of 300,000 potentially unneeded iframes may degrade performance. Removing this iframe should not affect portlet functionality since navigation is not as expected in a portal environment.
              Ken Fyten made changes -
              Fix Version/s 1.8.2-EE-GA_P03 [ 10251 ]
              Ken Fyten made changes -
              Affects [Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration]
              Assignee Priority P2
              Assignee Mircea Toma [ mircea.toma ]
              Ken Fyten made changes -
              Assignee Priority P2 P1
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #24216 Tue Mar 22 12:55:17 MDT 2011 mircea.toma ICE-6655 Changed core and component code generating iframes dynamically to use pseudo URLs. Introduced 'com.icesoft.faces.disableBrowserHistoryTracking' parameter to allow the disabling of back button detection, this also avoids having the history iframe from requesting pages from the server.
              Files Changed
              Commit graph MODIFY /icefaces/trunk/icefaces/bridge/src/status.js
              Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/DOMResponseWriter.java
              Commit graph MODIFY /icefaces/trunk/icefaces/bridge/src/synchronizer.js
              Commit graph MODIFY /icefaces/trunk/icefaces/bridge/lib/extras/autocomplete_ext.js
              Commit graph MODIFY /icefaces/trunk/icefaces/bridge/component/menu.js
              Hide
              Permalink
              Mircea Toma added a comment -

              Changed core and component code generating iframes dynamically to use pseudo URLs, this actually simplified alos the code since the URLs don't have to be resolved anymore.
              Introduced 'com.icesoft.faces.disableBrowserHistoryTracking' parameter to allow the disabling of back button detection, this also avoids having the history iframe from requesting pages from the server.

              To avoid having the history iframe pointing '.....xmlhttp/blank' URL the following context parameter needs to be added to web.xml file:

              <context-param>
              <param-name>com.icesoft.faces.disableBrowserHistoryTracking</param-name>
              <param-value>true</param-value>
              </context-param>

              Show
              Mircea Toma added a comment - Changed core and component code generating iframes dynamically to use pseudo URLs, this actually simplified alos the code since the URLs don't have to be resolved anymore. Introduced 'com.icesoft.faces.disableBrowserHistoryTracking' parameter to allow the disabling of back button detection, this also avoids having the history iframe from requesting pages from the server. To avoid having the history iframe pointing '.....xmlhttp/blank' URL the following context parameter needs to be added to web.xml file: <context-param> <param-name>com.icesoft.faces.disableBrowserHistoryTracking</param-name> <param-value>true</param-value> </context-param>
              Mircea Toma made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Hide
              Permalink
              Mircea Toma added a comment -

              When the history tracking is disabled the client (bridge) will not detect when the back button is used. So navigating back will bring up the page corresponding to the previous URL but with the content that the page had when loaded. Any content change that the previous page suffered due to any AJAX or push interaction is not restored.
              When history tracking is enabled and the back button is pressed the client (bridge) will fetch automatically the current content corresponding to the previous URL and apply that to the page.

              Show
              Mircea Toma added a comment - When the history tracking is disabled the client (bridge) will not detect when the back button is used. So navigating back will bring up the page corresponding to the previous URL but with the content that the page had when loaded. Any content change that the previous page suffered due to any AJAX or push interaction is not restored. When history tracking is enabled and the back button is pressed the client (bridge) will fetch automatically the current content corresponding to the previous URL and apply that to the page.
              Hide
              Permalink
              Ken Fyten added a comment -

              This needs to be tested using IE6 with HTTPS configured as well.

              Show
              Ken Fyten added a comment - This needs to be tested using IE6 with HTTPS configured as well.
              Ken Fyten made changes -
              Resolution Fixed [ 1 ]
              Status Resolved [ 5 ] Reopened [ 4 ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #24233 Wed Mar 23 18:28:51 MDT 2011 mircea.toma ICE-6655 Replace 'about:blank' URL with 'javascript:' pseudo-URL to avoid warnings when loading the page with IE6.
              Files Changed
              Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/DOMResponseWriter.java
              Commit graph MODIFY /icefaces/trunk/icefaces/bridge/src/synchronizer.js
              Hide
              Permalink
              Mircea Toma added a comment -

              It seems I've done the test in the past: http://jira.icefaces.org/browse/ICE-5123?focusedCommentId=27421&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_27421

              Show
              Mircea Toma added a comment - It seems I've done the test in the past: http://jira.icefaces.org/browse/ICE-5123?focusedCommentId=27421&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_27421
              Mircea Toma made changes -
              Status Reopened [ 4 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #24622 Thu May 19 06:10:14 MDT 2011 mircea.toma ICE-6655 Remove the modal popup regardless of its place in the stack of rendered popups.
              Files Changed
              Commit graph MODIFY /icefaces/trunk/icefaces/bridge/lib/extras/style.js
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Priority P1

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Tyler Johnson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: