Ajax features is a big part of client-side rendering. Not only do the
widgets support asynchronous requests, but every property can be updated
completely client-side -- you can redraw the entire widget if you wanted
to. (This is something we need to do in order to support DHTML, anyway.
It really fits well when rendering and/or updating subcomponents in a
widget.) Separating the widgets from the JSF framework is another reason
for introducing client-side rendering. When moving from JATO to JSF, the
components had to be completely rewritten -- the one thing that stayed
consistent was the CSS and JavaScript. By providing client-side
renderers, we can now begin using the widgets over PHP and Ruby.
However, we don't need to rewrite the components in order to do that.
That said, you may be interested in downloading a nightly build of
Woodstock 4.2. We have introduced more enhancements that put the latest
Woodstock performance within 93% of the 4.0 release. In particular, this
affects browser caching and large pages (e.g., where HTML tables are
used). The 4.1.1 release will also have these enhancements, but has not
been posted yet.
If you want to read more about the performance enhancements we've made,
take a look at the URL below.
https://woodstock.dev.java.net/servlets/ProjectForumMessageView?forumID=2879&messageID=21687
Dan
matroska wrote:
> Hi,
>
> I cannot find a reason to have client - side rendering. What are the
> advantages of this approach? Maybe to obtain ajax features? Made
> components rendered client side produces only very poor performance
> and big pages. Is there a way to enable server rendering with
> Woodstock 4.1? Woodstock 4.0 was fantastic and I would like to use
> the new version server side.
>
> Thanks
> John Slave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>