1. ICEmobile
  2. MOBI-616

Client Side App Cache Component State Saving


    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2 Final
    • Fix Version/s: None
    • Component/s: Faces, Spring
    • Labels:
    • Environment:


      We could leverage the HTML5 application cache for component state saving in both JSF and JSP frameworks. There are many cases where we should be saving state, such as when a tab (client-side true) or accordion is selected. This would solve several issues:

      - lack of server-side component state support in JSP
      - client-server synchronization issues after a page update. This is currently especially problematic when using SX, as SX uploads force a page refresh, which will reset component state, unless it's fully synchronized.
      - reducing server calls to update state. For instance, if we want to ensure that a tabset is not reset to the original tab on a page refresh, then we have to make server calls on every tab selection, which may not be necessary.

      Saving state in the application cache would also bring us closer to native app behaviour. When a user reopens a native app, they expect their application state to be maintained. This is usually hard to mimic with web applications, as it requires a lot of state to be maintained in the session, and/or also maintained across sessions. Saving state in the application cache would allow us to maintain state across sessions.


        There are no comments yet on this issue.


          • Assignee:
            Steve Maryka
            Philip Breau
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created: