On Fri, Nov 1, 2013 at 4:17 PM, Avraham Serour wrote:
> are you using sqlite?
No, I am using mysql.
--
Amanjot Kaur
Blog: kauramanjot35.wordpress.com
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop r
are you using sqlite?
On Fri, Nov 1, 2013 at 6:52 AM, amanjot kaur wrote:
> In my django app if two users are login in the same account and are
> registering two different clients then both the clients are added
> under the same client id but it should register under different client
> ids. So w
In my django app if two users are login in the same account and are
registering two different clients then both the clients are added
under the same client id but it should register under different client
ids. So what should I do for that.
--
Amanjot Kaur
Blog: kauramanjot35.wordpress.com
--
Y
On Tue, 2009-08-04 at 06:28 -0700, lfrodrigues wrote:
> Hi,
>
> I've developed a special Auth backend for a internal communication
> protocol. Everything was ok but now the requirements changed and I
> need to allow on the same browser (in diferent tabs) several logged
> users.
>
> How can I hav
Hi,
I've developed a special Auth backend for a internal communication
protocol. Everything was ok but now the requirements changed and I
need to allow on the same browser (in diferent tabs) several logged
users.
How can I have (in the same browser process) several logged users at
the same time?
On Sat, 2007-03-17 at 11:21 -0700, cwurld wrote:
> Does anyone know how the SESSION_EXPIRE_AT_BROWSER_CLOSE works? In
> other words, how does the Django session know the browser closed? It
> seems like this mechanism could be used to accomplish the above.
It's an HTTP cookie feature: if you don't
Does anyone know how the SESSION_EXPIRE_AT_BROWSER_CLOSE works? In
other words, how does the Django session know the browser closed? It
seems like this mechanism could be used to accomplish the above.
Chuck
--~--~-~--~~~---~--~~
You received this message because
I did it using PHP. It can be circumvented but it's not something
the average user would do. Everytime an user logins, the session id is
stored on a table, with the time and the user id. On every request by
every logged in user, I put every previous session ids from the user
id on an array, rem
> I would like to find a way to prevent users from simultaniously
> logging in from different computers but using the same username and
> password.
How do you define "different computers"?
A remote IP address, possibly cookies, and possibly JavaScript
are about all you have to work with to dete
The quick answer would be to check through
the session data for a matching user id, but
there's one possible wrinkle: How do you
know when a user has logged off?
In my case (not yet implemented), I'll have
a timeout, but that still doesn't address
the issue of a user losing a connection and
atte
Hi,
In order for users to use my Django site they must login. I am using
the standard auth app. I set the session to expire when the browser is
closed or when the user clicks a log out button.
I would like to find a way to prevent users from simultaniously
logging in from different computers but
11 matches
Mail list logo
