[ https://issues.apache.org/jira/browse/WICKET-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750091#comment-16750091 ]
ASF subversion and git services commented on WICKET-6563: --------------------------------------------------------- Commit d52371d8e294da4bdc475e4362667d1119752e4b in wicket's branch refs/heads/WICKET-6563 from Sven Meier [ https://gitbox.apache.org/repos/asf?p=wicket.git;h=d52371d ] WICKET-6563 update size when removing pages and keep pages in list for InMemoryPageStore, in case pages are not serialized and change their id afterwards > 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 > Reporter: Sven Meier > Assignee: Sven Meier > Priority: Minor > Fix For: 9.0.0 > > > 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)