Eelco Hillenius wrote: >> but why are these things tied to request threads? doesnt sound like they >> should be. >> > > If I understand Robert correctly that is due to an architectural > choice he just has to live with. Also, I'm wondering in what way > Tapestry is at fault here. I thought it had a decent reputation for > stability and performance. > > Eelco > > The implementation had been done using Tapestry 3. The ognl expressions are known to be slow. However upgrading to Tapestry 4 (and 5) is like changing to a different framework. Also the Tapestry 3 code was full of bugs and weird design constructs which you probably won't see if you don't have to go deep in the Tapestry code. I was impressed by the simplicity and modularity of Wicket so I would like to change to this.
Robert ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
