RE: architecture

Well this is true that JSF builds a sophisticated page model, which may
result in dramatic performance degradation. Many people noticed poor
performance when dealing with large data tables. 
JSF compared to ordinary JSP perform noticeably slower. The point is what
differences we talk about. For example - when we moved one of our
applications from webwork/JSP to JSF we noticed that the response time was
sometime 2 times longer, 8ms more CPU processing per request by average. If
we did that on a machine already serving more than 100 requests per second
we would probably feel the difference. However, because we served 3-4
requests per second the difference was barely observable. 

On the other hand - making attractive, dynamic AJAX interface was really
much simpler using JSF. Struts AFAIK (I rarely use it now, so I might have
missed something) don't have any notion of UI components. It won't help your
application to deal with UI changes. So building anything AJAX results in
writing two applications: one server side, and one javascript based client
side. And - by the way - this often performs better because you move part of
the application state to the browser and never store it on the server.

IMHO computing power expands much quicker than manpower, that's why less
performing solution often win.
Regards,

-----Original Message-----
From: SnowWolf Wagner [mailto:[email protected]] 
Sent: Monday, September 07, 2009 12:26 PM
To: [email protected]
Subject: Re: architecture

We utilize Struts 2.1.6 with the JSF plugin for when we want some of  
the features of jsf. While it is true that you can produce a jsf app  
faster today than a struts2, the struts app will preform better and  
use less resources. So the question the old one of balancing dev time  
vers long term operational cost.

T SnowWolf Wagner

On Sep 7, 2009, at 6:03 AM, measwel <[email protected]>  
wrote:

>
> Thank you Mike,
>
> That is exactly the type of architecture I was thinking about; jsf  
> 2.0 +
> seam + facelets + spring + hibernate. The only thing I was concerned  
> about,
> was the scalability of jsf 2.0. I understand, that it should not be a
> problem, as long as the applicaton is not ill-designed. I am trying  
> to get
> my IDE set up for using these technologies right now.
>
> Take care,
> Marek
> -- 
> View this message in context:
http://www.nabble.com/architecture-tp25319857p25328026.html
> Sent from the java.net - webwork users mailing list archive at Nabble.com 
> .
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]