It is not request based if you use a backing bean value to bind it to.
<h:panelGroup rendered="#{empty treeStateBean.bufferedHtml}">
<t:buffer into="#{treeStateBean.bufferedHtml}">
...
</t:buffer>
</h:panelGroup>
<h:outputText value="#{treeStateBean.bufferedHtml}" escape="false" />
Deploy treeStateBean to the application scope.
-Andrew
On 12/14/06, Dave <[EMAIL PROTECTED]> wrote:
<t:buffer> is per response based, and can not be shared between requests or
between users. So it can not improve performance. Am I right?
Andrew Robinson <[EMAIL PROTECTED]> wrote:
may work. Just put the tree in it and only render the
buffer if the backing bean value that you store it in isn't already
set.
On 12/13/06, Dave wrote:
> I have some performance issues with MyFaces. It tooks 500 miliseconds to
> render a tree2(not very big). Its tree data model is buffered and shared
by
> all users. It is quite expensive just to render the tree. I am wondering
if
> I can buffer the rendering to improve performance because the tree is
> immutable, and shared by all users.
>
> Thanks
> Dave
>
> ________________________________
> Have a burning question? Go to Yahoo! Answers and get answers from real
> people who know.
>
>
________________________________
Have a burning question? Go to Yahoo! Answers and get answers from real
people who know.
