[
https://issues.apache.org/jira/browse/WICKET-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358900#comment-15358900
]
Giannis Koutsoubos commented on WICKET-6177:
--------------------------------------------
[~mgrigorov] I setup a naive implementation of your comment above, for the sake
of simplicity I reused the PageAccessSynchronizer in order to verify the base
logic of the implementation
The code based on your sample is available below
https://github.com/koutsoub/wicket-samples/blob/master/WICKET-6177/src/main/java/com/mycompany/AsyncPageStore.java
https://github.com/koutsoub/wicket-samples/blob/master/WICKET-6177/src/main/java/com/mycompany/AsyncPageStorePageManagerProvider.java
Will the above do the trick?
Lock the page when serialization is requested, unlock the page when
serialization completes.
Can we reuse the PageAccessSynchronizer for this logic (if so we could extend
the WicketSession in order to use the provider there) or implement a
PageSerializerSynchonizer in the same principles?
> 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.4#6332)
