Author: Krokador | Posted on: 9/22/2009 7:18:27 AM | Views : 442

I don't evne know where to begin the search or even if I'm posting in the right place for this, but any feedback/input on this would be appreciated. Here's the deal:
We adapted an old PC Application into a web application with asp.net, and have trouble running into our user's head that it is a web application and thus takes a little more time to load and isn't exactly the same as what they had before. (There were reasons for the move to web I'M not going to go into anyway.).
We already crammed into the application something very similar to a screen lock. Thanks to some tweaking and crackin', we managed to require a password input, keep the session active for X time and prevent the use of back and next buttons, f5, and the likes. Just like an application lock would do on a PC app.
Yet that's not enough. In the environment the users are in, they were used to have two or more instances of the app running, logging into 2 different accoun ...

Go to the complete details ...