You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/05/03 18:23:00 UTC
[jira] [Commented] (WICKET-6563) Rework page and data storage
[ https://issues.apache.org/jira/browse/WICKET-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832725#comment-16832725 ]
ASF subversion and git services commented on WICKET-6563:
---------------------------------------------------------
Commit 2cbc73e9b023b554b324ff155420b261f9d606b5 in wicket's branch refs/heads/master from Sven Meier
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=2cbc73e ]
WICKET-6563 allow usage as cache and as persistent store
> Rework page and data storage
> ----------------------------
>
> Key: WICKET-6563
> URL: https://issues.apache.org/jira/browse/WICKET-6563
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 9.0.0-M1
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 9.0.0-M1
>
>
> IPageManager, IPageStore and IDataStore are riddled with complicated and error-prone code aiming to do one simple thing: keeping pages around.
> There are multiple problems with the current implementation:
> * PageStoreManger does too muchÂ
> ** it handles request and session storage
> ** it contains workarounds for DiskDataStore, when the sessionId changes
> * IPageStore/AbstractPageStore
> ** has no access to IPageManagerContext
> ** juggles with byte[], serialization and conversion
> * IDataStore introduces an unncecessary third layer into the API
> Additional or specialized stores are difficult to implement.
> We should rework that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)