myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabrielle Crawford (JIRA)" <>
Subject [jira] Commented: (TRINIDAD-1487) Improve the application view cache
Date Thu, 03 Dec 2009 21:38:20 GMT


Gabrielle Crawford commented on TRINIDAD-1487:

Removing the AVC for Trinidad 2.0:

> Improve the application view cache
> ----------------------------------
>                 Key: TRINIDAD-1487
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Improvement
>            Reporter: Matthias We├čendorf
> We need to improve the "Application View Cache" feature.
> However, the issue is that at the very least, we would need to:
> 1) Switch to using per-page flags to turn it on.  The default is off.  This
> allows customers to explicitly turn on the AVC
> 2) Come up with  a replacement for cases where we will break the AVC--for
> example any renderer that stores rendering information on a component
> (including the UIViewRoot)
> Detecting the cases where we are doing 2 is hard and still leaves possible
> problems with other renderers, or potentially the application itself.  We
> might be able to do some autodetection for UIXComponent cases by integrating
> with the FacesBean in a similar way to the delta state saving, but we would
> still need to handle non-Trinidad Components like the UIViewRoot and it is
> possible that the application could still hose itself.  In general, the kinds
> of failures that the application will see with the application view cache
> will not be obviously caused by the setting.
> Currently the "application view cache" is not supported.
> Once the Facelets support has improved we can see how much faster
> the cache is than Facelets before we decide whether it is worthwhile to make
> the investment necessary to make the application view cache acceptably
> robust.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message