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 Marinschek (JIRA)" <de...@myfaces.apache.org> on 2007/09/24 16:49:52 UTC
[jira] Commented: (MYFACES-1731) Application scope JSF tree buffer
to improve performance and reduce memory
[ https://issues.apache.org/jira/browse/MYFACES-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529879 ]
Martin Marinschek commented on MYFACES-1731:
--------------------------------------------
Hi Dave,
the problem is that you can change the tree - with component-bindings, etc. So you can't have an application scoped tree. For JSF 2.0, something like this is currently discussed. Until then, we can only reduce state-saving per user, not entirely remove it.
You'll see something like this come up in Bernhard Huemer's Google SoC project, you might want to check out Trinidad for optimized state-saving, or check out the PSS parameters in MyFaces. Putting optimized state-saving right in the components is currently the best solution, though, everything else is just an approximation.
regards,
Martin
> Application scope JSF tree buffer to improve performance and reduce memory
> --------------------------------------------------------------------------
>
> Key: MYFACES-1731
> URL: https://issues.apache.org/jira/browse/MYFACES-1731
> Project: MyFaces Core
> Issue Type: Improvement
> Environment: ALL
> Reporter: Dave
>
> For a big JSF page that is accessed by thousands of users, the JSF tree needs to be rebuilt everytime a user accesses the page.
> If there is a way to configure the page so that the page JSF tree is built only once and put it in application scope, and shared by all users, it will save memory and improve performance. The backing bean data saved with JSF tree can be separated from JSF tree and stored in user's session scope.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.