Now I understand you :-)
Hi Andrea,
I understood you. But it seems you didn't understand me :-)
Component rendering is currently not pluggable, i.e. you cannot set a
different strategy and any of the IXyzSettings and use different code
to do the rendering. Unless this is refactored to be pluggable there
is no sense to think in this direction. JDK6 users will not be able to
use Wicket if Wicket is build with JDK7.
On Tue, Jul 5, 2011 at 5:52 PM, Andrea Del Bene<adelb...@ciseonweb.it> wrote:
My fault Martin, I have not explained well myself. I try to summarize what I
wanted to say:
-Java 7 introduces some tools to implement Fork/Join parallelism (
http://en.wikipedia.org/wiki/Fork-join_queue )
-Should we adopt this pattern? Is Wicket ready for implementing such a
pattern?
Render phase is probably the most time-expensive part of Wicket. Do you
think it could be splitted in subtasks?
For example it would be nice if a page could apply Fork/Join parallelism to
render its children components.
