Can it be optional, with a context param ?
On Mon, Feb 4, 2013 at 9:36 AM, Leonardo Uribe <lu4...@apache.org> wrote: > Hi > > Some time ago, this proposal was submitted to the consideration of this > list. > > [core][proposal] JSF View Pooling (going beyond JSF Stateless Mode) > > http://markmail.org/message/54rb3aphc6txwzbr > > I have been thinking about the advantages and disadvantages of this > technique. > > Advantages: > > - Build view time is cut off, giving a speed improvement per each requests. > Test done shows around 8% improvement in page rendering and in ajax case > the improvement is even better, because in that case the build view time > has more weight. > - A lot less objects are allocated. > > Disadvantages: > > - Detection technique to enable this optimization is not 100% fail-safe. > - It could create memory fragmentation, making garbage collection slower. > - Higher memory footprint. > - It is difficult to keep the code synchronized between versions of JSF, > because each concept related to view handling affects how the view pool > works. > - The use ui:param uses EL VariableResolver, makes the view non poolable, > because the ValueExpression instances are not stateless in this case. > > Do the advantages justify the introduction of this concept? Will users find > the improvement useful or applicable in real projects? or does not worth > the complexity involved and in this case keep thing simple is better? > > regards, > > Leonardo Uribe > > -- > [image: http://download.irian.at/2013/CONFESS_2013_email_signature.png] -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
