On Jan 19, 2008 5:18 AM, Martijn Lindhout <[EMAIL PROTECTED]> 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?
Stateless pages can be a good option for things like public home pages etc; pages where you don't have a crazy amount of functionality, but that get hit hard. More interesting imho than the scalability argument is that such stateless pages are always bookmarkable. This makes them very useful for e.g. login pages, where you can expect clients to directly go to, or maybe have in the background for an extended time before actually using it. Read about it here: http://cwiki.apache.org/WICKET/stateless-pages.html and take a look at org.apache.wicket.examples.stateless in wicket-examples. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
