On 2/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
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:
ehmmm i dont think this will really work quite right for the most ajax calls. Because the page that is constructor is really in the constructed state So for this to work you have really store the state of the page somehow everytime you do an ajax request. And if there are quite a lot of ajax request for a pretty big page. I wouldn't want to construct it everytime (and fully initialize it)
* 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.
Yes this could work but then Session is really not thread save! Now it semi safe (except for the attach/detach methods) For this we just can remove the Session lock object from the RequestTarget. Because all else are already stopped at the Session.get page call. * I think it opens the way for comet style behaviors. i think comet style works much better on session pages. johan
