Hello,
In searching for some posts on ViewState in the WebTree I came across this post that talks about using a WARP panel along with the TreeControl. Rather than add on to that post, I have a question that I think is related.
I have a Tree that I populate through Manual demand load, no callbacks. The data can get quite large, and I noticed that as I expand nodes on the tree that the ViewState grows quite large over time. This eventually results in the WARP panel either timing out or just plain not returning the data. I have increased the WARP callback timeout from the default 20 seconds to 40 seconds, but I don't think this is the solution. You now only wait longer until the hourglass disappears.
Short of turning ViewState off, which does not offer a pretty solution (everything disappears) is there a better way to manage the ViewState in this situation?
Thanks in advance for any suggestions,
Dan
OK - to answer my own post here, I decided to jettison the WARP panel and change my tree to use Manual-Smart Callbacks. I had to do some tweaking on my code, as we were relying heavinly on some of the node properties that were no longer there, but if you think it through its not too difficult to do. I passed a little more info in the DataPath property, and then rebuilt the node properties when necessary.
The performance screams, the viewState is tiny, and it was not nearly as difficult as I thought it would be.
So, if a growing ViewState size is a problem for your app you may want to consider this approach.
Cheers,Dan
Thanks for sharing this information, as it may prove helpful for someone in the future.
Most people don't want to go through the effort of implementing ManualSmartCallbacks on WebTree, since putting it in a WARP is generally easier to do. This provides a good reason to use ManualSmartCallbacks instead.