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.
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.
--
View this message in context: http://www.nabble.com/What-about-html-renderer-in-woodstock-4.1--tf4935484.html#a14154051
Sent from the Project Woodstock - Users mailing list archive at Nabble.com.