Last post Dec 02, 2010 08:42 AM by roopeshreddy
Nov 04, 2010 05:49 PM|artsnob|LINK
I've just completed my first iPhone-compatible & Droid-compatible mobile app. At one time, I was confounded by differences in back button behaviour between the two platforms, but I came up with a suitable workaround.
One thing remains that I'd like to correct if it's at all possible. The application is very session-variable dependent, so naturally, its very dependent on sessions. Users invariably use leave pages open when they turn off their smartphones, and this means
that they return to a non-repsonsive timed-out page when they turn it back on. Can anything be done to preclude this? As in active web app or no web app?
mobile asp.net style
mobile application development
Nov 05, 2010 03:23 AM|roopeshreddy|LINK
If the user closes the browser unexpectedly or left it or turn off the mobile, no event is raised on server side or client side. You can only set the session Timeout, so that if the web page is unresponsive for that time, it automatically gets invalidated.
You can invoke Session.Abandon() method to invalidate session, when he clicks logout.
That's the main reason, all bank sites asks to logout properly or don't use the invalidated sessions.
Nov 14, 2010 11:16 AM|artsnob|LINK
Thanks, could you elaborate a bit on what invalidated translates to in terms of the user POV? Say the user shuts off a smartphone while on a page in one of your mobile web sites that contains code. An hour later, he turns it back on again. Is the behavior
Nov 14, 2010 11:38 AM|roopeshreddy|LINK
if the session validation is checked in the server code, then you can redirect to a page, where the session invalidated information is shown. otherwise, the beviour is unpredictable.
Hope it helps u...
Nov 17, 2010 01:33 PM|artsnob|LINK
Thanks again. The redirection you mention is just what I need. You don't happen to know of any documentation/article on that session validation in the server code technique, do you? I did a pretty thorough web search, and couldn't come up with anything.
Have you ever actually done this yourself?
Nov 18, 2010 07:55 AM|roopeshreddy|LINK
Check the following links,
Dec 01, 2010 01:59 PM|artsnob|LINK
Excellent links, thanks! I've marked your reply as the answer.
Of course a good answer begets new questions. As in: Which one of the several approaches did you opt for? What time out value seems to work best for you? Is there a mobile website of yours or one that you know of where I can observe the technique in
action? (I.E., one where I can make the timeout message appear?) Thanks for your continuing assistance.
Dec 02, 2010 08:42 AM|roopeshreddy|LINK
Ideal timeout is 15-20 minutes based on your requirements. We use to keep 20 minutes as session timeout. I can't provide my project link, bcoz Customer is using in his own network, i mean internal network.
Once the session is timed out, you can redirect to a specific page and display the error - "Session Expired. Relogin again".
To practically check this, login in to any Bank websites.
Hope it helps u..