Yes. If you don't want people to log back in after session timeout.
Use a window.setInterval to call "something" back on the server in that Application space, otherwise your session timeout will kick in and your app will be forced to re-authenticate. However, if this is what you want (
i.e. your single page will send back a message saying they need to log in - and your _javascript_ will handle it) then that is also an option.
In general, part of what may be needed in an AJAX app is a regular task that will go back to the server to get any "new" information. This same function can obviously be used for the keep-alive if the space between calls is smaller than the session timeout. The same concept can be used even if the rest of the webpage is not AJAX.
Regards,
Gary
On 8/22/05, Chad Renando <[EMAIL PROTECTED]> wrote:
A guy on the cfajax yahoo group asked an interesting question, figured
I'd fire it to ya' all, given that the cfajax group is pretty quiet
at the best of times...
I have an app where, once you log in, does everything on the same .cfm
page. In some areas, a lot of the functionality occurs without
refreshing the page using Ajax (yeah, lame misguided acronym for old
technology, but let's not debate).
So the Q: Do I need to refresh my login session within my Ajax
functions to keep them alive?
Chad
who feels the American-ism "ya'all" does not translate well into email
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
