Still, if you know what you are doing non-detachable models may be appropriate. For example, I have used them for some slow-to-get database query results. But I also wrote my own custom cached page invalidator to make sure these results do not stay around for too long.
Regards, Erik. Jonathan Locke wrote: > Non-detachable models probably are not the best way to work > with a database. And since they can't be detached, your whole > model stays in the session the whole time, while the detachable > ones shrink to a few bytes (object header + id + transient slot) > when they are detached by Wicket after each request. > > -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ ------------------------------------------------------------------------- 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