As always, the caveat is that you should avoid premature optimization like the plague. Until you've got a handle on your scaling problem (and it probably is that and not a performance problem) and you know what needs to be tuned, the best policy is probably to just build something simply and quickly in order to discover if you even have a problem that requires this solution.
Martijn Lindhout wrote: > > Hi guys, > > In the release notes, I read: "stateless pages and components for those > parts of your application that needs to scale to extremely large numbers > of > users". > > Does somebody use this feature or is it somewhere documented? What do I > have > to do and what are the differences from a 'normal' wicket app? > > Regards, > > -- > Martijn Lindhout > JointEffort IT Services > http://www.jointeffort.nl > [EMAIL PROTECTED] > +31 (0)6 18 47 25 29 > > -- View this message in context: http://www.nabble.com/Stateless-pages-and-performance-tp14970238p14975570.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
