Just as a side note, for one project, I would receive a user token, and pass this to server-side methods so the server could identify who I was if it needed to find info, AND it used this to determine I was logged in. Wasn't much of a deal for me...just didn't know if there was a better way.
----- Original Message ----- From: "JesterXL" <[EMAIL PROTECTED]> To: "Flexcoders" <[email protected]> Sent: Tuesday, February 08, 2005 10:53 AM Subject: [flexcoders] Session Management & Authentication As a Flash Developer, I know that I can manage sessions myself, since I have the data all the time without page refreshes, and the server can just remain a bunch of methods that do the serious heavy lifting whilst I manage all of the state in the front end client. However, the server needs authentication, and thats why the server-side team here wants to manage sessions. I DO agree with their logic in that managing a session for authentication purposes after a login makes sense... but authenticating every method call doesn't seem realistic. Most of my work in the past has been for fat clients using Flash, so typically the container (C, VB) would manage the authentication. What are you all doing? Still managing sessions 100%, letting Flex keep application state, or just keeping login authentication? I read some one was using a keep alive, didn't know for what purpose. Thanks if you can help! --JesterXL Yahoo! Groups Links
