You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Thomas Heigl (JIRA)" <ji...@apache.org> on 2017/04/06 07:55:41 UTC
[jira] [Commented] (WICKET-6177) Blocking page serialization
[ https://issues.apache.org/jira/browse/WICKET-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958497#comment-15958497 ]
Thomas Heigl commented on WICKET-6177:
--------------------------------------
Hi,
I'm very interested in this issue and gave the implementation a test-run yesterday.
My application is currently configured to use {{HttpSessionDataStore}}. {{AsynchronousPageStore}} fails when used with this data store. Maybe there should be an additional check that the {{IDataStore}} supports asynchronous storing before wrapping the page store with the asynchronous implementation?
-t
> Blocking page serialization
> ---------------------------
>
> 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
> 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)