advatogiageft
New Member
I'm currently in the planning/early building phase of a desktop flex application that will be communicating to a Zend Application on a web server.The flex app will basically be like a layout/view in terms of the MVC pattern, it will make requests to various controller actions and display the data returned in a meaningful way, and post data that will update various data in the database on the server.Basically what I'm wondering is what the best way is to go about building a login system for the desktop application. Hopefully I'm correct in assuming that I can't use the regular channels that you would if your users were accessing the application via a browser, so I was thinking I would do this:[*]Flex app posts login details (email, password) to a login action[*]The login action uses Zend Auth to check if the details are valid[*]The login action creates a unique hash (and stores it in the db somewhere along with the user's id) and returns a json object containing the hash along with the user's id to the flex app[*]Whenever the flex app makes requests to any action in the web app, it also sends along the user's id and the unique hash so the web app can verify the user.Does this make sense, or am I barking up the wrong tree here?Let me know what you think, and whether there's a better solution I should look into.Thanks!