> While sorting is most often done by the database, I don't think Wicket's > design should assume this is where sorting will be done. Wicket should leave > that up to the application developers.
Sure, we don't assume that. However, we do assume that you're not using models for massive sorting either. It's not their purpose to support that, and PropertyModels in particular are written as convenience over the cost of a slight performance penalty. That penalty gets big with sufficient large data sets, but it is unrealistic to have such large datasets in the first place (because that won't render in browsers, and will be seriously bad for you bandwidth usage). Eelco
