myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Myfaces Wiki] Update of "Working With DataTable And PreserveDataModel" by powhwee
Date Thu, 02 Feb 2006 02:06:42 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The following page has been changed by powhwee:
http://wiki.apache.org/myfaces/Working_With_DataTable_And_PreserveDataModel

------------------------------------------------------------------------------
  
  Lastly, the Render phase will occur just equal as decribed before...
  
- What are the implications about this approach? Consider the case of having preserveDataModel
set to "false" and clicking on the "next" click to navigate to the next bunch of data. As
described above, the data from the backend will be requested in the APPLY REQUEST VALUES phase,
so lately in the UPDATE MODEL phase the changes will be applied to the data recently retrieved
from the backend, which is not guaranteed to be the same as the one the user was seeing before
clicking on the link. In resume, maybe we are working with stale data (big problem, indeed).
+ What are the implications about this approach? Consider the case of having preserveDataModel
set to "false" and clicking on the "next" click to navigate to the next bunch of data. As
described above, the data from the backend will be requested in the APPLY REQUEST VALUES phase,
so later in the UPDATE MODEL phase the changes will be applied to the data recently retrieved
from the backend, which is not guaranteed to be the same as the one the user was seeing before
clicking on the link. In short, maybe we are working with stale data (big problem, indeed).
  
  But if we take the same approach, but using preserveDataModel to "true", the data used to
update the model will be exactly the same that the client was seeing before, so we can be
sure that no strange behaviour occurs. (Please note that this does not prevent from having
and old version of the data, as it might have changed between these requests...).
  

Mime
View raw message