The specific problem occurs when a session times out on a "Web
2.0"/ ajax page. Links that use XMLHttpRequest are being properly
redirected to 'app.timeout', but the result is placed inside the
container originally meant for the XMLHttpRequest result, including
double headers, etc.
How does one properly handle app.timeout and other redirections in
a Web 2.0 environment where the expected result is a chunk of html
but the result is a fully rendered page?
What I do is return the text "###timeout###" when an Ajax request
results in a session timeout, instead of redirecting to app.timeout.
In my Javascript Ajax response handler I look for that string in
transport.responseText and if I find it I set window.location to the
app.timeout url, which redirects to top level page to the right place.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
