You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2011/05/12 00:21:48 UTC
[jira] [Created] (MYFACES-3138) Simplify ResponseStateManager
implementation code
Simplify ResponseStateManager implementation code
-------------------------------------------------
Key: MYFACES-3138
URL: https://issues.apache.org/jira/browse/MYFACES-3138
Project: MyFaces Core
Issue Type: Sub-task
Components: JSR-314
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
ResponseStateManager implementation deals with state / structure logic, but this is not valid anymore, because that is now an implementation detail.
We need to clean up all that code and just let a simple and efficient implementation there, so we can move to the next step.
Additionally, it could be good to create StateCacheFactory abstraction to deal with client /server differences, and divide StateCacheImpl into two, apply strategy pattern (because now we understand clearly how the algorithm should work).
Now StateCache is StateCache<K,V> where K is the token that allow it to restore the state V.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MYFACES-3138) Simplify ResponseStateManager
implementation code
Posted by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe resolved MYFACES-3138.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.6
> Simplify ResponseStateManager implementation code
> -------------------------------------------------
>
> Key: MYFACES-3138
> URL: https://issues.apache.org/jira/browse/MYFACES-3138
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: JSR-314
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.0.6, 2.1.0
>
>
> ResponseStateManager implementation deals with state / structure logic, but this is not valid anymore, because that is now an implementation detail.
> We need to clean up all that code and just let a simple and efficient implementation there, so we can move to the next step.
> Additionally, it could be good to create StateCacheFactory abstraction to deal with client /server differences, and divide StateCacheImpl into two, apply strategy pattern (because now we understand clearly how the algorithm should work).
> Now StateCache is StateCache<K,V> where K is the token that allow it to restore the state V.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira