Author: knopp
Date: Thu Sep 10 00:54:26 2009
New Revision: 813186
URL: http://svn.apache.org/viewvc?rev=813186&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=813186&r1=813185&r2=813186&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
Thu Sep 10 00:54:26 2009
@@ -31,7 +31,7 @@
before the rendering actually begins.
Every listener-interface link contains the render-count. Every time listener
interface request handler is invoked
-there's a check in place that throw StalePageException when the link is stale.
+there's a check in place that throws StalePageException when the link is stale.
Later in game we can have fancy detection that immediately (matter of seconds)
tells user that the page he sees
become stale (because same page was rendered in another tab/window). This can
be achieved by a cookie containing
