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 "GSoC2010_StateSavingPerformanceImprovements" by Marius Petoi
Date Wed, 07 Apr 2010 13:14:13 GMT
Dear Wiki user,

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

The "GSoC2010_StateSavingPerformanceImprovements" page has been changed by Marius Petoi.
http://wiki.apache.org/myfaces/GSoC2010_StateSavingPerformanceImprovements?action=diff&rev1=15&rev2=16

--------------------------------------------------

  
  At the moment, the saved state contains the component tree together with properties for
each component (a list of its children and facets, together with the list of listeners, the
behaviours map, etc). Every component is responsible for creating its own “state” object,
which is afterwards included in the parent’s state object. In the end, the “state” of
the UI''''''View''''''Root and the tree of components is saved in the External''''''Context.
The actual state is written in the response by Response''''''Manager objects. The Response''''''Manager
used so far is the Html''''''Response''''''State''''''Manager, which writes to the response
the HTML code representing the actual saved state. Also, this manager object retrieves the
state from the external context, when a request is received.
  
- Upon restore, the UI''''''View''''''Root is constructed using the information stored in
the External''''''Context and using the existing UI''''''View''''''Root (the UI''''''View''''''Root
from the last request).
+ Upon restore, the UI''''''View''''''Root is constructed using the information stored in
the External''''''Context and using the existing UI''''''View''''''Root (the UI''''''View''''''Root
from the last request). This is done in the Restore View phase of the JSF lifecycle.
+ 
+ On the other hand, all component classes implement the interface Partial''''''State''''''Holder,
which extends State''''''Holder. State''''''Holder is an interface which contains methods
for saving and loading state. Its extension, Partial''''''State''''''Holder contains three
extra methods: clear''''''Initial''''''State, initial''''''State''''''Marked and mark''''''Initial''''''State,
which help to the implementation of partial state saving. All components that have a partial
saving of their state implement this interface. The difference between full state and partial
state is made using two wrapper marker classes: _Attached''''''State''''''Wrapper and _Attached''''''Delta''''''Wrapper.
+ 
+ In the Application object, a State''''''Manager is held. The actual state manager used at
the moment is Jsp''''''State''''''Manager''''''Impl. In the restore view phase of the JSF
lifecycle, the "restoreView"  method of the State''''''Manager is invoked. This retrieves
the State''''''Management''''''Strategy, which traverses the component tree and for each of
the components restores its state(this means that the "restoreState" metod of the component
is invoked). Also the tree of components is updated by taking into account the added and removed
components. Upon saving, the added and removed components are saved, as well as the difference
in state for each of the components. For each of the components, the "save''''''State" method.
  
  This project is intended to take a deeper look into what exactly is saved at the moment.
The saved state should be analyzed and see whether anything can be skipped. For this, memory
profiling should be done and see which part of the saved state occupies the most memory. Afterwards,
we should see how much of this is really used and what can be dismissed.
  

Mime
View raw message