is it possible to be able to log out when u closer the internet window.....this would help at school....in our library we have 40 computers and i always for get to log out ....then when i go back i cant remember which ones i didnt log out on....is it possible to put an auto log out function under my settings?
If you do not have this option selected under site settings (the default is off) :
"Enable multiple browsers to be logged into the same account"
you can just log in to any other machine to log out all other browsers that remain logged in. So, if you are concerned, just log in, and then out of ANY machine.
-Russ
Originally posted by TDR1For a school's shared computer, your school's IT person should have setup the PC to automatically delete cookies on exit. If not, then accedental persitance of user data becomes a valid concern to all users of the PC. Shame on that IT person!
is it possible to be able to log out when u closer the internet window.....this would help at school....in our library we have 40 computers and i always for get to log out ....then when i go back i cant remember which ones i didnt log out on....is it possible to put an auto log out function under my settings?
Originally posted by TDR1This is true.
so russ....if im logged into my computer at home and if i have unchecedk 'Enable multiple browsers to be logged into the same account'....then when i log in at school it will log me out at home...and vice versa???
It was introduced to help people in your situation some time back.
The other option is only for users who use a number of machines of which they only have access.
-Russ
Russ, could an auto log-out be enabled (at minimum workload for you) by setting an 'auto log-out' flag in my settings somewhere, and for those with it turned on to use a per-session cookie rather than the standard more durable chap? I'm no expert on these things, so I've no idea whether that would be simple or not.
Originally posted by RussAuto log out works by IP address, I guess ...is that correct ?? . So auto log out might not work if a player plays on different machines which are NATed behind a router, or firewall .
This is true.
It was introduced to help people in your situation some time back.
The other option is only for users who use a number of machines of which they only have access.
-Russ
Could this feature be made to look for different MAC address ... Just curious...
Cheers
Originally posted by pidermanDon't be confused (as I once was) when people talk about session variables. Commonly people refer to server side variables that are unique for each user as they browse around a site as session variable. But on the stateless web, you need an id on the client to identify which session is yours - and guess what is commonly used (like, 99.99% of the time), you guessed it, cookies!
I think that would need a 'no cookies' setting, whereby you only use session variables instead of cookies. This is also used on many forums where you can check a 'login automatically' option. If you don't check it, you are logged out automatically when you close your window, or 'session'.
So it all comes back to cookies at the end of the day.
-Russ
Originally posted by ToeThis could be done - it would not be a huge effort to implement this.
Russ, could an auto log-out be enabled (at minimum workload for you) by setting an 'auto log-out' flag in my settings somewhere, and for those with it turned on to use a per-session cookie rather than the standard more durable chap? I'm no e ...[text shortened]... ese things, so I've no idea whether that would be simple or not.
-Russ
Originally posted by RussIndeed. But it is not, as you think, 99.99%. For if that would be the case, all the people who choose not to have cookies wouldn't be able to order from a web store. There is a good alternative, and that is to propagate the session ID in the URL of the page. Then you have no cookies, but still a session.
Don't be confused (as I once was) when people talk about session variables. Commonly people refer to server side variables that are unique for each user as they browse around a site as session variable. But on the stateless web, you need an id on the client to identify which session is yours - and guess what is commonly used (like, 99.99% of the time), you guessed it, cookies!
So it all comes back to cookies at the end of the day.
-Russ