Another way would be to create a central Object which dispatches Login/Logout events. Every view, which is interested in such an event, can register itself to this object. In case of the Logout event it simply resets its data.
Cheers,
Ralf.
On 8/4/06, Doug Arthur <[EMAIL PROTECTED]> wrote:
I've built a system that utilizes a login/logout process. The login portion works great. I realize now that my app is 95% complete, that when logout is executed, all it really does is change states, clear the user singleton instance, but what I didn't realize was going to be a challange is how to globally log them out so that data throughout the app is wiped clean slate, and when another user logs in, they won't get the previous users data.I've tried all the initialize,creationComplete,updateComplete, and oher methods and they don't do the trick.Thanks!
--
Ralf Bokelberg <[EMAIL PROTECTED]>
Flex & Flash Consultant based in Cologne/Germany __._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
