[ https://issues.apache.org/jira/browse/WICKET-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966662#comment-15966662 ]
ASF subversion and git services commented on WICKET-6177: --------------------------------------------------------- Commit 2ffd587dea4c5e1edec0853f35a9b5761e391917 in wicket's branch refs/heads/master from manuelbarzi [ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=2ffd587 ] WICKET-6177 Blocking page serialization > Introduce AsynchronousPageStore > ------------------------------- > > Key: WICKET-6177 > URL: https://issues.apache.org/jira/browse/WICKET-6177 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 7.4.0 > Environment: any > Reporter: Martin Makundi > Assignee: Martin Grigorov > Labels: serialization > Attachments: 6177.tgz, Wicket_Quickstart_7.zip > > Original Estimate: 168h > Remaining Estimate: 168h > > We have a performance issue with our Wicket app, page serialization causes > inconvenience to user because PageStoreManager.storeTouchedPages() blocks the > request until pageSerializer.serialize(page) has been handled. > Could this be solved by serializing the page in a separate thread and let the > request complete? > The problem we have is that user is making quick small ajax modifications to > the page but serialization + network latency makes the delay very > inconvenient. If serialization could be done in separate thread, user would > feel only the network delay which is bearable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)