users@woodstock.java.net

Re: What about html renderer in woodstock 4.1?

From: Dan Labrecque <Dan.Labrecque_at_Sun.COM>
Date: Tue, 04 Dec 2007 08:52:30 -0800

jsr wrote:
> Winston Prakash wrote:
>
>> Actually I created the jar to test the performance between HTML
>> rendering and Client side rendering.
>> I did not find too much performance degradation.
>>
>>
>
> Try doing some large tables with several hundred rows. IE will hang for a
> minute or two while it maxes out your CPU trying to render the page. Firefox
> handles it slightly better.
>

This is why I recommend downloading Woodstock 4.1.1 when it becomes
available. We have addressed this particular issue for large HTML tables.

>
> Winston Prakash wrote:
>
>> Apart from slight performance problem, Client side rendering is what
>> you need to write next gen web 2.0 application.
>>
>>
>
> I agree that client side rendering is needed, however, I don't believe it
> should be the only option. The fact is that most people will only needed
> AJAX functionality in a few places, if at all. Rendering every item
> client-side is simply not needed. Even if you look at Dojo's own web page,
> you'll see that most of it is regular HTML with only the necessary parts
> being rendered on the client.
>
> Ideally, I'd like to see the components always default to server-side HTML
> rendering and have a checkbox/attribute for rendering it client side. This
> would allow the developer to mix and match and get the best possible
> performance and features for their individual needs.
>

If you don't need Ajax functionality, simply set the webuiJsfx attribute
to false for the head tag. (There are other attributes to customize the
JavaScript even further.) Although client-side rendering is still used,
certain JavaScript files are omitted from the page. This includes some
JavaScript for both Woodstock and Dynamic Faces.

Unfortunately, we're not going to be able to support both HTML and
client-side rendering. Considering that Woodstock 4.1.1 is within 93% of
download speeds for the 4.0 release, it no longer provides any
significant gains. And we still want to move away from being tied to the
JSF renderers in order to support other frameworks.

Dan