Hi all,
One thing preventing my Silverlight application being of an acceptable level of quality to release to our customers is Timeouts. Basically, our customers are known to leave the application open in their browser after using it, going off and doing something else, and then returning later on to use it again. By this time, the authentication context has disappeared, so as soon as they do something, it raises exceptions. The only way to resolve it when this happens is to close the application in the browser an start again. Now, we could extend the session to be for 24 hours, as the web site is recycled overnight anyway, however this reduces scalability as all those resources are locked unnecessarily. We could also use a timer to timeout the page before the session times out. This can be complicated, because we have to make sure that every user event resets the timer. Again, an undesirable. So I guess my question is, to create a rock solid Silverlight application, and given that Silverlight has a far superior eventing system to asp.net, is it possible to hook something in to the Session Ended event that I can use to redirect back to the login page or perform some action? Regards, Tony Wright Director / Principal Consultant Hazaa Pty Ltd m: +61 424 225 393 | e: <mailto:[email protected]> [email protected] | w: <http://www.hazaa.com.au/> http://www.hazaa.com.au
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
