Author: buildbot
Date: Mon Feb 10 17:00:31 2014
New Revision: 897183

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/jsf.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 10 17:00:31 2014
@@ -1 +1 @@
-1566675
+1566681

Modified: websites/staging/deltaspike/trunk/content/jsf.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/jsf.html (original)
+++ websites/staging/deltaspike/trunk/content/jsf.html Mon Feb 10 17:00:31 2014
@@ -90,7 +90,9 @@
 </ul>
 </li>
 <li><a href="#lazy">LAZY</a><ul>
-<li><a href="#examples">Examples</a><ul>
+<li><a href="#advantage_1">Advantage</a></li>
+<li><a href="#disadvantage_1">Disadvantage</a></li>
+<li><a href="#workflow-example">Workflow example</a><ul>
 <li><a href="#first-get-request-with-windowid">First GET request with 
windowId</a></li>
 <li><a href="#first-get-request-without-windowid">First GET request without 
windowId</a></li>
 <li><a href="#further-get-request-with-windowid">Further GET request with 
windowId</a></li>
@@ -172,7 +174,7 @@
 <h2 id="available-modes">Available modes</h2>
 <h3 id="clientwindow">CLIENTWINDOW</h3>
 <p>Each GET request results in an intermediate small html page which checks if 
the browser tab fits the requested windowId. <br/>
-When the windowId is valid, a unique token (called <code>dsRid</code>) for the 
current request will be generated and added to the URL. <br/>
+When the windowId is valid, a unique token (called <code>dsRid</code>) will be 
generated for the current request and added to the URL. <br/>
 In addition a cookie with with the dsRid/windowId will be added. On the server 
side, the verified windowId will be takes from the cookie.</p>
 <h5 id="advantage">Advantage</h5>
 <ul>
@@ -183,6 +185,7 @@ In addition a cookie with with the dsRid
 <li>Every GET requests streams the the windowhandler.html first -&gt; The
     application probably feels a litte bit slower</li>
 </ul>
+<p><br/></p>
 <h4 id="change-windowhandlerhtml">Change windowhandler.html</h4>
 <p>To customize the look &amp; feel of the windowhandler.html, you can simply 
provide a own via:</p>
 <div class="codehilite"><pre><span class="nd">@Specializes</span>
@@ -204,7 +207,16 @@ On the first GET request without a windo
 The current windowId will be stored in the <code>window.name</code> variable 
on the client side. <br/>
 For all further requests, a lazy check will be performed to check if the 
windowId in the URL is matching with the <code>window.name</code>.
 If it's not matching, the view will be refreshed with the right windowId in 
the URL.</p>
-<h4 id="examples">Examples</h4>
+<h5 id="advantage_1">Advantage</h5>
+<ul>
+<li>No windowhandler.html / loading screen required</li>
+</ul>
+<h5 id="disadvantage_1">Disadvantage</h5>
+<ul>
+<li>It could happen that 2 tabs will share the same windowId for 1 request 
because the <code>LAZY</code> mode will check lazily, after rendering the view, 
if the windowId matches the <code>window.name</code>. Therefore it could happen 
that @ViewAccessScoped or other scopes will unintentionally be destroyed. </li>
+</ul>
+<p><br/></p>
+<h4 id="workflow-example">Workflow example</h4>
 <h5 id="first-get-request-with-windowid">First GET request with windowId</h5>
 <ul>
 <li>Renders the view</li>
@@ -228,7 +240,6 @@ If it's not matching, the view will be r
 <li>Renders the view</li>
 <li>If it does not match, reload the URL with the right windowId taken from 
<code>window.name</code></li>
 </ul>
-<p>TODO: Contra</p>
 <p><br/></p>
 <h3 id="none">NONE</h3>
 <p>Any window or browser tab detection will be disabled for the current 
request.<br/>


Reply via email to