[
https://issues.apache.org/jira/browse/WICKET-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476293
]
Johan Compagner commented on WICKET-201:
----------------------------------------
No this already doesn't happen anymore at least for the saving.
Because the save thread is high prio! It can keep up with anything the other
request do.
I think matej did test it with many more sessions and loads of iterations (up
the 1000)
And in the current situation the 2 threads can keep up with both.
Serialization already works this way, if request comes in for a page. And the
page is still not serialized
(so the serialization thread couldn't keep up) then the request thread already
helps with serialization of the page.
And because of saving thread is high prio that one can keep up with the saving
as far as we (matej and i) have could test it.
> refactor storing pages and versions
> -----------------------------------
>
> Key: WICKET-201
> URL: https://issues.apache.org/jira/browse/WICKET-201
> Project: Wicket
> Issue Type: Bug
> Reporter: Eelco Hillenius
> Assigned To: Johan Compagner
> Priority: Critical
> Fix For: 1.3, 2.0
>
>
> See http://www.nabble.com/refactor-storing-pages-and-versions-tf2943670.html
> for a discussion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
