On Sun, 25 Jan 2009, Johan Compagner wrote: > I guess wicket should dump the page serialized size in development > mode. So that users see them when developing.
Yep, we have in one project debug logging doing just that so you more or less notice right away when something starts to hog memory. I've also thought of fail-fast by making an assertion in a DiskPageStore subclass or some such place that would crash if the size is too big. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
