Well, I've had serious trouble making that work. :-)
I believe that rationale is:
- large trees --> serverside is faster
- small trees --> client side is faster
Reason is the entire tree is carried through the wire with client-side.
Yesterday's experiments revealed that you have to be very careful
setting the tree properties: if you choose clientside, you also have
to set preserveToggle="true", otherwise it won't work. (bug in state
handling)
Wolf
On 10 Sep 2006, at 14:36, Christopher Cudennec wrote:
Hi,
did anyone manage to keep the state of the tree2 with client side
toggle enabled? I prefer to use client side toggling because it's
much faster than the server side one. I think there must be a way by
JavaScript and/or Ajax...
Thanks,
Christopher
