You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by we...@apache.org on 2007/05/23 23:20:38 UTC
svn commit: r541092 -
/myfaces/current/orchestra/core/src/site/xdoc/bestPractice.xml
Author: werpu
Date: Wed May 23 14:20:37 2007
New Revision: 541092
URL: http://svn.apache.org/viewvc?view=rev&rev=541092
Log: (empty)
Modified:
myfaces/current/orchestra/core/src/site/xdoc/bestPractice.xml
Modified: myfaces/current/orchestra/core/src/site/xdoc/bestPractice.xml
URL: http://svn.apache.org/viewvc/myfaces/current/orchestra/core/src/site/xdoc/bestPractice.xml?view=diff&rev=541092&r1=541091&r2=541092
==============================================================================
--- myfaces/current/orchestra/core/src/site/xdoc/bestPractice.xml (original)
+++ myfaces/current/orchestra/core/src/site/xdoc/bestPractice.xml Wed May 23 14:20:37 2007
@@ -18,8 +18,7 @@
<p>
In various tests and implementations it became clear very early that the best approach
- is, to have a single page controller under one conversation for one or many pages
- depending on your scope flow.
+ is, to have a single page controller under one conversation for one page in most cases.
</p>
<p>
The reason for this self imposed limitation is that if you end up with too many conversations