You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Haimberger (JIRA)" <de...@myfaces.apache.org> on 2007/02/24 18:48:05 UTC
[jira] Created: (MYFACES-1541) Partial State Saving improvement to
myfaces
Partial State Saving improvement to myfaces
-------------------------------------------
Key: MYFACES-1541
URL: https://issues.apache.org/jira/browse/MYFACES-1541
Project: MyFaces Core
Issue Type: Improvement
Components: General
Affects Versions: 1.1.6-SNAPSHOT
Reporter: Martin Haimberger
Fix For: 1.1.6-SNAPSHOT
Partial State Saving of the Component Tree to reduce the needed bandwith if client side state saving is activated or the used memory if server side state saving is used. There are two "modes" in which the partial state saving can be used, the faster one is if the jsp is only rendert once and a "template" of the component tree is generated and saved. The following request uses this "template" to construct the UIViewRoot and merge the partial state save. Before the state will get saved, the current UIViewRoot is compared to the template and only the components which differs are saved. In the secound mode the JSP is processed by every request, which is very usefull if Scripts are embedded inside the page. The secound reason is backword compatiblity because for example the f:loadbundle tag will load the bundle if the TAG is processed. The s:loadBundle component solves this problem, but if someone want to use partial state saving and is not willing to include the sandbox for the s:loadBundle component the secound mode will help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1541) Partial State Saving improvement to
myfaces
Posted by "Martin Haimberger (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Haimberger updated MYFACES-1541:
---------------------------------------
Status: Patch Available (was: Open)
> Partial State Saving improvement to myfaces
> -------------------------------------------
>
> Key: MYFACES-1541
> URL: https://issues.apache.org/jira/browse/MYFACES-1541
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General
> Affects Versions: 1.1.6-SNAPSHOT
> Reporter: Martin Haimberger
> Fix For: 1.1.6-SNAPSHOT
>
>
> Partial State Saving of the Component Tree to reduce the needed bandwith if client side state saving is activated or the used memory if server side state saving is used. There are two "modes" in which the partial state saving can be used, the faster one is if the jsp is only rendert once and a "template" of the component tree is generated and saved. The following request uses this "template" to construct the UIViewRoot and merge the partial state save. Before the state will get saved, the current UIViewRoot is compared to the template and only the components which differs are saved. In the secound mode the JSP is processed by every request, which is very usefull if Scripts are embedded inside the page. The secound reason is backword compatiblity because for example the f:loadbundle tag will load the bundle if the TAG is processed. The s:loadBundle component solves this problem, but if someone want to use partial state saving and is not willing to include the sandbox for the s:loadBundle component the secound mode will help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.