atom feed8 messages in org.apache.myfaces.dev[core][discuss] Is it worth to includ...
FromSent OnAttachments
Leonardo UribeFeb 4, 2013 9:35 am 
Grant SmithFeb 4, 2013 5:28 pm 
Leonardo UribeFeb 4, 2013 5:45 pm 
Walter MourãoFeb 5, 2013 1:45 am 
Thomas AndraschkoFeb 5, 2013 2:04 am 
Leonardo UribeFeb 5, 2013 1:55 pm 
Thomas AndraschkoFeb 8, 2013 9:31 am 
Mark StrubergFeb 8, 2013 10:40 am 
Subject:[core][discuss] Is it worth to include Stateless JSF / View Pooling concept into MyFaces?
From:Leonardo Uribe (lu4@apache.org)
Date:Feb 4, 2013 9:35:46 am
List:org.apache.myfaces.dev

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,