I am thinking the time when login timeout is being used, especially in the same session (same browser session) when using. I have completed many sites recently, I've added a 60-minute timeout and they are creating problems, as the users are not able to fill a large form (such as depositing for a resume - People do not copy a copy to resume through another program or part)
But on other sites, such as Facebook, it seems that on one site, I have a div / p To continue the pushup in the current session, the user has been forced to enter his password. Never remember your password until you are using the same browser window.
The main reason I usually use the timeout is to ensure that the data is safe, such as the other party, sit on the computer after a few hours and not use the system as the original user.
I'm thinking how will you decide when a site should be excluded from users due to inactivity?
I am thinking that the answer will be unknowable.
IMO, they are valid when:
- Security is important ( I.e. banking)
- The possibility of seat-swapping is high (i.e. public terminal)
Regardless of your resume system can be examples like, where you can see the public terminals People want O to be able to do something that they can deactivate for longer than your desired or required timeout period. Yes
I think you have to handle it in a smart fashion - or the way they can get the data in a hurry (which will be ace, spending an hour for filling out a form is not fun - Can he just upload one file?), Or to ensure that they can continue to damage the data without getting any signal after logging in to log in again.
Comments
Post a Comment