ICEfaces
  1. ICEfaces
  2. ICE-3905

optimize DocumentStore.save calls

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8DR#1
    • Fix Version/s: 1.8RC1, 1.8
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      ICEfaces, compressDOM
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.)

      Description


      DocumentStore.save is called twice during user input when compressDOM is enabled, first in applyBrowserDOMChanges and again at the end of the cycle. See ICE-3618.

        Activity

        Ted Goddard created issue -
        Ted Goddard made changes -
        Field Original Value New Value
        Salesforce Case []
        Fix Version/s 1.8DR#3 [ 10143 ]
        Ken Fyten made changes -
        Salesforce Case []
        Affects [Documentation (User Guide, Ref. Guide, etc.)]
        Assignee Priority P2
        Assignee Ted Goddard [ ted.goddard ]
        Ken Fyten made changes -
        Salesforce Case []
        Component/s Framework [ 10013 ]
        Ken Fyten made changes -
        Comment [ Not sure what needs documenting, assigned to Ted. ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #18181 Fri Jan 16 15:51:46 MST 2009 ted.goddard Document cache call to delay fast infoset compression (ICE-3905)
        Files Changed
        Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/BridgeFacesContext.java
        Hide
        Ted Goddard added a comment -

        DocumentStore.cache(Document document) now keeps the document in memory until a call to save(). This allows applyBrowserDOMChanges to leave the DOM in memory for later processing.

        Note that a sequence of cache() calls must always be followed by a save() call on the same request for the compression to take effect.

        Show
        Ted Goddard added a comment - DocumentStore.cache(Document document) now keeps the document in memory until a call to save(). This allows applyBrowserDOMChanges to leave the DOM in memory for later processing. Note that a sequence of cache() calls must always be followed by a save() call on the same request for the compression to take effect.
        Ted Goddard made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Fix Version/s 1.8 [ 10161 ]
        Assignee Priority P2
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Assignee Ted Goddard [ ted.goddard ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved: