Hi,

I agree with this. Ajaxanywhere execute whole processing of jsf lifecycle, but it responsed back to client only part of the page (ajax zone which client declare). So I suppose that it should works a little faster. But I want to know how Myfaces works with Facelets, is it really better to use Facelets instead of JSP?

 

Thanks,

Yura.


From: Cagatay Civici [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 26, 2006 12:27 AM
To: MyFaces Discussion
Subj
ect: Re: How to speed up JSF

 

Hi,

As far as I know, ajaxanywhere submits the page as a whole actually, not just the zones(spans) and the zone components output spans. These spans' innerHtmls are later retrieved from the wrapped servletresponse and set using _javascript_. This approach will not help your application to run faster.

What do you think?

Cagatay,

On 3/25/06, Yura.Tkachenko <[EMAIL PROTECTED] > wrote:

Hi,

I just finding some ways to speed up JSF. I'm using MyFaces implementation and actually I don't like how JSF is rendering it's very slow. I've never tried Facelets with MyFaces is it really can speed up work of my application? Because I have only little theoretical knowledge about Facelets. But on all my JSF pages I actually doesn't use JSP as it, so I suppose I have always some time to: compile JSP(only 1 time) + execute jsp compiled class. So I think if Facelets miss this step then my application will work much faster, am I right?

+ Another approach to use AjaxAnywhere with this library server response executes much faster, because user requests not all page, only part of it.

Anyone use Facelets+MyFaces+AjaxAnyWhere – is it faster for user then only MyFaces?

 

Thanks,

Yura Tkachenko

Murano Software Kharkov, Ukraine

mailto: [EMAIL PROTECTED]

http://www.muranosoft.com

 

 

 

Reply via email to