On 8 May 2009, at 16:35 , veeravendhan wrote:
> Duplicate login should not done is my requirement. with the username
> one login shoud be happend, if another user is trying to login in the
> system, he should be informed this login is currently in use.
>
> Thanks
> Veera
This doesn't really make
Duplicate login should not done is my requirement. with the username
one login shoud be happend, if another user is trying to login in the
system, he should be informed this login is currently in use.
Thanks
Veera
On Apr 1, 11:43 am, Briel wrote:
> Hi.
> You don't really
http://docs.djangoproject.com/en/dev/topics/http/sessions/#session-expire-at-browser-close
On Apr 1, 2:26 am, veeravendhan wrote:
> Say a user is logged in to the system, If he closes the browser how
> will I handle the Logout for that user ? Any idea ??
Hi.
You don't really have to log the user out, unless you are making
something with very sensitive material. A lot of sites wont log you
out unless you haven't been at their site for some time.
One thing you could do, would be to log users out that haven't
been active for x minutes/hours, but
Say a user is logged in to the system, If he closes the browser how
will I handle the Logout for that user ? Any idea ??
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
5 matches
Mail list logo