Yeah - the resources thing can't be what Matt was talking about. That doesn't have anything to do with scalability, and is easily solved in quite a few different ways.
Anyway, for now this is just an unsubstantiated claim. Could I write a Wicket application that was slow and hard to scale? ABSOLUTELY! Could I write one that was fast and easy to scale? CERTAINLY! Cold hard numbers are the only thing I believe. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Oct 14, 2009 at 2:19 PM, Matej Knopp <matej.kn...@gmail.com> wrote: > On Wed, Oct 14, 2009 at 9:16 PM, dtoffe <dto...@yahoo.com.ar> wrote: > > > > Perhaps this is the original report of performance problems: > > > > http://techblog.molindo.at/2008/08/wicket-interface-speed-up.html > That's hardly a scalability issue. > > -Matej > > >
