Hi all, It should be possible to define stateless behavior(listener)s now, i.e. ajax behaviors that override getStatelessHint and let it return true. So if you design your page to be stateless (only put stateless components in them), Wicket should be able to (re)construct the component tree that is need to serve the ajax call. If this works, this is great for the following reasons:
* Obviously there are use cases out there where you want to build that super spike resistant page where you still want to use ajax rather than normal requests. * We don't have to synchronize stateless requests on the session. Johan/ others... we probably sync such requests now anyway, right (at least if a session is already available as otherwise it would be done on a throwaway object in which case it doesn't matter)? If we do, this would be a nice optimization that can considerably increase the throughput of such pages. * When you take the case where you have a very resource heavy request, where you first want to display part of the page while getting the heavy part in via Ajax, you can actually use a non-blocking ajax request (i.e. to a stateless ajax behavior on a stateless page, which would be the first part to display) to prepare that request, without the need to do the processing in a separate thread. Which has pros and cons compared to doing it in a separate thread for sure, but it is nice to have the alternative. * I think it opens the way for comet style behaviors. Thoughts? Eelco
