Mailing-List: contact commits-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 06 Apr 2010 08:45:09 -0000
Message-ID: <20100406084509.25703.66333@eos.apache.org>
Subject: 
 =?utf-8?q?=5BMyfaces_Wiki=5D_Update_of_=22GSoC2010=5FStateSavingPerforman?=
 =?utf-8?q?ceImprovements=22_by_Marius_Petoi?=

Dear Wiki user,

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

The "GSoC2010_StateSavingPerformanceImprovements" page has been changed by =
Marius Petoi.
http://wiki.apache.org/myfaces/GSoC2010_StateSavingPerformanceImprovements?=
action=3Ddiff&rev1=3D6&rev2=3D7

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

  =

  =3D=3D Description =3D=3D
  =

- In JSF 2.0 there is the possibility to partially save the state of the pa=
ge in the ExternalContext. This means that at the first request the entire =
state is saved, but afterwards only the differences from this are saved. My=
Faces2 introduces the =E2=80=9CState''''''Management''''''Strategy=E2=80=9D=
, which is an interface for strategies used for saving and respectively loa=
ding the view. The default MyFaces strategy implemented so far, upon saving=
 the view checks whether there has been a previously saved view. If so, it =
saves just the differences between the old state and the new, actual state.=
 If not, the entire state is saved in the external context request map.
+ In JSF 2.0 there is the possibility to partially save the state of the pa=
ge in the External''''''Context. This means that at the first request the e=
ntire state is saved, but afterwards only the differences from this are sav=
ed. MyFaces2 introduces the =E2=80=9CState''''''Management''''''Strategy=E2=
=80=9D, which is an interface for strategies used for saving and respective=
ly loading the view. The default MyFaces strategy implemented so far, upon =
saving the view checks whether there has been a previously saved view. If s=
o, it saves just the differences between the old state and the new, actual =
state. If not, the entire state is saved in the external context request ma=
p.
  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 re=
sponsible for creating its own =E2=80=9Cstate=E2=80=9D object, which is aft=
erwards included in the parent=E2=80=99s state object. In the end, the =E2=
=80=9Cstate=E2=80=9D of the UI''''''View''''''Root and the tree of componen=
ts is saved in the External''''''Context.
  Upon restore, the UI''''''View''''''Root is constructed using the informa=
tion stored in the External''''''Context.
  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 pa=
rt of the saved state occupies the most memory. Afterwards, we should see h=
ow much of this is really used and what can be dismissed.