Martijn Dashorst <[EMAIL PROTECTED]> writes: > > All, > When just trying out something Ruud and Marco did, I got this strange > 'underbelly' feeling that we should look at one tiny problem: how to > handle expired sessions when doing an Ajax call. > When doing partial page rendering, the expired session page is rendered > into the component hierarchie, which doesn't look too good. > The developer of the ajax page should be aware of such an event > happening, but is there some errorcode we could return instead of a > page? > Martijn-- Living a wicket life...Martijn Dashorst - http://www.jroller.com/page/dashorstWicket 1.1 is out: > http://wicket.sourceforge.net/wicket-1.1
I agree about letting the developer know somehow. I have an auto-complete component using Scriptaculous and there is no indication that the session has expired. I must not be handling something probably, but if the session has expired, and the first action performed after the timeout is to type into a auto-complete field, nothing happens, ie. there is no response to the user. In my application, not until a navigation to another page is done will the timeout page appear. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
