Okay, I see what you're saying. I think it would be cool to have it work like this: run through the Iterator from the DataSource and, using pks, determine if the current list exactly matches the one from the last request. If so, do nothing. Otherwise, re-render the whole thing. This way the list is re-rendered only when needed, and always when needed.
I think it would be best to put the pk method in the DataSource. It's trivial to implement and adds a lot to what we can do with the list. Are you actually writing this code? If so, I'd love to help out if it's committed somewhere. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
