[
https://issues.apache.org/jira/browse/MYFACES-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396838#comment-13396838
]
Leonardo Uribe commented on MYFACES-3563:
-----------------------------------------
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.
> Improvements in State Saving Algorithm
> --------------------------------------
>
> Key: MYFACES-3563
> URL: https://issues.apache.org/jira/browse/MYFACES-3563
> Project: MyFaces Core
> Issue Type: Improvement
> Components: JSR-314
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Attachments: MYFACES-3563-1.patch, MYFACES-3563-5.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
