Author: knopp
Date: Sat Aug 15 17:40:28 2009
New Revision: 804494
URL: http://svn.apache.org/viewvc?rev=804494&view=rev
Log: (empty)
Modified:
wicket/sandbox/knopp/experimental/wicket-ng/src/main/java/org/apache/wicket/page/page-management.txt
Modified:
wicket/sandbox/knopp/experimental/wicket-ng/src/main/java/org/apache/wicket/page/page-management.txt
URL:
http://svn.apache.org/viewvc/wicket/sandbox/knopp/experimental/wicket-ng/src/main/java/org/apache/wicket/page/page-management.txt?rev=804494&r1=804493&r2=804494&view=diff
==============================================================================
---
wicket/sandbox/knopp/experimental/wicket-ng/src/main/java/org/apache/wicket/page/page-management.txt
(original)
+++
wicket/sandbox/knopp/experimental/wicket-ng/src/main/java/org/apache/wicket/page/page-management.txt
Sat Aug 15 17:40:28 2009
@@ -17,6 +17,12 @@
So why is versioning disabled during render in Wicket? What can
actually change? RenderCount detects
changes that would normally result in version bump but they don't
because they happen during render.
What are those changes?
+
+UPDATE:
+ Versioning is disabled during page render (i.e.
IRedirectRenderer). That also includes onBeforeRender
+ call that can rebuild component hierarchy but it doesn't
increment version (otherwise there would be a
+ new version each time user refreshes a page with listview).
This is where render count can detect that
+ page version rendered in one tab is stalled because it was
rerendered in another.
How to detect this?
