ICEfaces
  1. ICEfaces
  2. ICE-5149

Configurable update coalescing

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.8.2
          • Fix Version/s: 1.8.2-EE-GA, 1.8.3
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces
          • Affects:
            Documentation (User Guide, Ref. Guide, etc.)

            Description

            When several updates are available for a particular element, ICEfaces will coalesce these (based on the element ID) into the latest update. This is a performance optimization that avoids overwhelming clients that are unable to retrieve updates as quickly as the server can generate them. In some cases, however (such as for a component that records changes from the last time it was rendered) this update coalescing should not be performed.

            Then intent of this JIRA is to provide a configuration parameter for turning off update coalescing. A more fully-featured implementation might allow coalescing to be configured selectively for different components or regions of the page.

              Activity

              Ascending order - Click to sort in descending order
              Ted Goddard created issue -
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #19724 Wed Nov 18 10:36:18 MST 2009 ted.goddard configurable coalesceUpdates (ICE-5149)
              Files Changed
              Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/command/UpdateElements.java
              Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/BridgeFacesContext.java
              Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/PushModeSerializer.java
              Hide
              Permalink
              Ted Goddard added a comment - - edited

              Set coalesceUpdates to false to turn off the update coalescing optimization. This is useful for custom components that make non-idempotent changes to the DOM (changes that depend on previous renders, not just the current state of the component).

              <context-param>
              <param-name>com.icesoft.faces.coalesceUpdates</param-name>
              <param-value>false</param-value>
              </context-param>

              Show
              Ted Goddard added a comment - - edited Set coalesceUpdates to false to turn off the update coalescing optimization. This is useful for custom components that make non-idempotent changes to the DOM (changes that depend on previous renders, not just the current state of the component). <context-param> <param-name>com.icesoft.faces.coalesceUpdates</param-name> <param-value>false</param-value> </context-param>
              Ted Goddard made changes -
              Field Original Value New Value
              Salesforce Case []
              Fix Version/s 1.8.2-EE [ 10216 ]
              Fix Version/s 1.8.3 [ 10211 ]
              Hide
              Permalink
              Ted Goddard added a comment -

              Note that this optimization is not directly relevant to ICEfaces 2.0. ICEfaces 2.0 applies a notify/refresh strategy, so a full render pass takes place once the notification has been accepted (updates are not queued up on the server waiting for the client). In this case the coalescing occurs prior to rendering via redundant notifications being handled via a single refresh. There should be no problem with non-idempotent component output under the notify/refresh strategy.

              Show
              Ted Goddard added a comment - Note that this optimization is not directly relevant to ICEfaces 2.0. ICEfaces 2.0 applies a notify/refresh strategy, so a full render pass takes place once the notification has been accepted (updates are not queued up on the server waiting for the client). In this case the coalescing occurs prior to rendering via redundant notifications being handled via a single refresh. There should be no problem with non-idempotent component output under the notify/refresh strategy.
              Ken Fyten made changes -
              Salesforce Case []
              Affects [Documentation (User Guide, Ref. Guide, etc.)]
              Ted Goddard made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Ted Goddard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: