|
|
Posted by Alan Little on 07/20/55 11:39
Carved in mystic runes upon the very living rock, the last words of
frizzle of comp.lang.php make plain:
> alvonsius wrote:
>> How about scenario like this ..
>> If user A is login into the system, the database write the use log,
>> userid, timestamp, blah blah ... and the when user B login with the
>> same account the system automatically do the logout action for the
>> user A and tell him what's happened (like "dude, some other user is
>> logging with your same account") ... then we give the user chance to
>> re-login and kick user B plus protect user A from kicking ...
>>
>> Humm ... my english is suck ... I can't give clear explanation ...
>> but I hope you get the idea ...
>>
>> About cron, I think that wasn't bad idea ... user should know about
>> the session expiration in the Term of Service. If they agree with
>> that ... I think it is OK ... plus, we owned the site and what we do
>> is simply to protect them, right ...
>
> Why not prevent user B from logging in, and not kicking user A?
What happens if user A goes to the library, logs in to the site, forgets
to log out, and now wants to log in at home?
--
Alan Little
Phorm PHP Form Processor
http://www.phorm.com/
Navigation:
[Reply to this message]
|