> The main purpose for this would be to track login collisions
> and make sure users aren't sharing log in info.
>
> If a user has a high number of collisions we can assume they
> are sharing their credentials and take the appropriate
> actions.
There are plenty of legitimate reasons for login c
The main purpose for this would be to track login collisions and make sure
users aren't sharing log in info.
If a user has a high number of collisions we can assume they are sharing their
credentials and take the appropriate actions.
-- Sent from my Palm Pre
Tim Chase wrote:
> So is there a
> So is there a viable django solution for this problem?
To build on what Malcolm was saying, the problem you have is that
the only things your server knows are (1) when a user last
engaged in a transaction with your server and optionally (2) when
a user has intentionally logged out. #2 is ni
On Fri, 2009-07-31 at 20:56 -0700, django user wrote:
> So is there a viable django solution for this problem?
You can implement your own session support. It's not that difficult.
Django is just a layer on top of Python, so there's a Django solution to
any computable problem. Django's default con
So is there a viable django solution for this problem?
On Jul 31, 7:50 pm, Malcolm Tredinnick
wrote:
> On Fri, 2009-07-31 at 19:43 -0700, django user wrote:
> > I'm interested in a solution for this as well.
>
> > I am thinking that a good way might be to rewrite the auth middleware
> > to check
On Fri, 2009-07-31 at 19:43 -0700, django user wrote:
> I'm interested in a solution for this as well.
>
> I am thinking that a good way might be to rewrite the auth middleware
> to check and see if a user login for this user exists and if it does
> then remove that login and log in the current u
I'm interested in a solution for this as well.
I am thinking that a good way might be to rewrite the auth middleware
to check and see if a user login for this user exists and if it does
then remove that login and log in the current user. A message could
then be passed to the login page letting th
On Fri, Jul 31, 2009 at 08:04:50AM -0700, When ideas fail wrote:
> Is there a way i can stopped people who are already logged in logging
> in again?
My initial thought - this sounds risky - for a website.
How do you know if the user is already logged in?
The computer they were using may have di
On 31 Jul 2009, at 17:04 , When ideas fail wrote:
>
> Hello, if i am using this generic view in my urls.py?
>
> (r'^accounts/login/$', 'django.contrib.auth.views.login',
> {'template_name': 'myapp/login.html'}),
>
> Is there a way i can stopped people who are already logged in logging
> in again?
I would like to do something like this, too!
Please help!
On Fri, Jul 31, 2009 at 5:04 PM, When ideas
fail wrote:
>
> Hello, if i am using this generic view in my urls.py?
>
> (r'^accounts/login/$', 'django.contrib.auth.views.login',
> {'template_name': 'myapp/login.html'}),
>
> Is there a way
Hello, if i am using this generic view in my urls.py?
(r'^accounts/login/$', 'django.contrib.auth.views.login',
{'template_name': 'myapp/login.html'}),
Is there a way i can stopped people who are already logged in logging
in again?
Thanks
--~--~-~--~~~---~--~~
Yo
11 matches
Mail list logo
