First article is outdated, so not a valid reference to consider now.
Regarding second article, I disagree with that since every web
framework has some sort of lifecycle to process the request and
generate the response, why is it a problem that JSF has one too. Also
session is not specific to JSF, it's developer's responsibility
to use memory efficiently.
Finally I suggest you taking a look at JSF 2.0. Here's a good article;
http://andyschwartz.wordpress.com/2009/07/31/whats-new-in-jsf-2
On Sep 6, 2009, at 2:12 PM, Richard Yee wrote:
First of all, the blog post is three years old. The article may have
had some valid points at the time, but the implementations have
improved and the technology is understood better now. JSF 2.0 also
has a lot of new features that improve on the weak spots in the
previous specs too.
Richard
Sent from my iPhone
On Sep 6, 2009, at 5:07 AM, measwel <[email protected]>
wrote:
Hereby the links:
http://debasishg.blogspot.com/2006/09/which-web-framework-do-you-want-to-use.html
http://www.thomasknierim.com/108/web-development/jsf-scalability/
Please comment.
--
View this message in context:
http://www.nabble.com/JSF-scalability-issues--tp25310548p25317142.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
