This content has been marked as final. Show 5 replies
You might be able to use a SharedObject to write a flag to file. When the user successfully logs in, write their username (but NOT their password) to the SharedObject. The app should check for the SharedObject file at app startup, and if the user is logged in, don't show the login screen.
Someone else might have a different approach. Using a SharedObject can have its problems, like what if the user logged in and then closed the browser, in that case you would prefer to delete the SharedObject, but if they close the browser I don't know if you can Flex apps perform such pre-close operation.
Is there any other way to solve this problem?
Local Shared Object is the Flex solution.
Actually, your users will learn pretty fast not to hit F5. There is no reason for them to do that anyway. Why do you think this will be a problem?
Refreshing the browser window reloads the application, so naturally it will display the login screen. The same goes for when the users use the back button and go to a different site then go forward back to your application.
Setting a Local Shared Object is the solution for you if you want to maintain a session.