Ah, I understand. Perhaps the easiest way to solve this problem is to
create a custom session handler that uses the login ID as the key for
the session. You can't have more than one session with the same login
ID that way, so that stops multiple logins.
what do you mean exactly by custom
Preventing multiple logins is not an easy task to solve without a
please don't make me afraid :-) i assumed this being rather
easy, as soon as i have access to the session table (and the
data, s.above)
i wonder, if there is already an auth system providing the prevention
of multiple logins.
my auth system is more or less selfmade. i dig the session component
very much, but need more control in my controllers (!) over the
content
of the session table.
1) i need to find arbitrary session entries in the db,
or better: retrieve a row with a particular serialized
value of data.
do i
On 4/5/07, jyrgen [EMAIL PROTECTED] wrote:
my auth system is more or less selfmade. i dig the session component
very much, but need more control in my controllers (!) over the
content
of the session table.
1) i need to find arbitrary session entries in the db,
or better: retrieve a row
1) i need to find arbitrary session entries in the db,
or better: retrieve a row with a particular serialized
value of data.
I'm curious as to what you're trying to accomplish by doing this?
should read deserialized data, sorry. let me try to explain:
after successful login i write a
On 4/5/07, jyrgen [EMAIL PROTECTED] wrote:
should read deserialized data, sorry. let me try to explain:
after successful login i write a status value logged_in = 1
into the session. this helps granting access to certain actions.
Users should be allowed to log in only *once*. so during
