Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.15, 2.1.9
    • Component/s: JSR-314
    • Labels:
      None

      Description

      Following the improvements done in:

      MYFACES-3117 Current server state saving implementation prevents multi-window usage

      Which included also:

      MYFACES-3134 Move all code related to state caching into one place
      MYFACES-3137 Align ResponseStateManager implementation with the spec
      MYFACES-3138 Simplify ResponseStateManager implementation code

      It is possible to improve this part a lot more. The are some parts of the code that works fine but are too old and are not very well understood. I think it is reasonable to review this part in deep. Note this could suppose some changes in ServerSideStateCacheImpl, and other related classes.

      Our PSS algorithm is very good, but these changes are more related to the logic involved in save/restore the state for both modes client side and server side state saving.

      It is possible to imagine a "mixed" strategy between client side and server side state saving that could reduce the session size and in that way, achieve an even better scalability. Also, it is possible to imagine way to secure the token sent in the view when server side state saving is used using a random number, allowing to disable encryption in such cases.

      1. MYFACES-3563-6.patch
        73 kB
        Leonardo Uribe
      2. MYFACES-3563-5.patch
        73 kB
        Leonardo Uribe
      3. MYFACES-3563-1.patch
        60 kB
        Leonardo Uribe

        Activity

        Hide
        Johanes Sungarda added a comment -

        Dear all, Please apologize for my mistake. I'm just browsing around and accidentaly click on wrong button.

        Show
        Johanes Sungarda added a comment - Dear all, Please apologize for my mistake. I'm just browsing around and accidentaly click on wrong button.
        Hide
        Leonardo Uribe added a comment -

        First prototype not ready for commit.

        Show
        Leonardo Uribe added a comment - First prototype not ready for commit.
        Hide
        Leonardo Uribe added a comment -

        Second prototype. It has a better design to isolate the logic related to the key serialized into the map, and the token returned to be encoded into the state. The idea is change SerializedViewKey into an abstract class, and create private implementations customized to be as small as possible.

        Show
        Leonardo Uribe added a comment - Second prototype. It has a better design to isolate the logic related to the key serialized into the map, and the token returned to be encoded into the state. The idea is change SerializedViewKey into an abstract class, and create private implementations customized to be as small as possible.

          People

          • Assignee:
            Leonardo Uribe
            Reporter:
            Leonardo Uribe
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development