> 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 session handler ? wouldn't it
suffice
to declare a session model in this fashion
class mySession extends AppModel {
var $name = 'mySession';
}
now i can access the sessions table. but still unsolved: un-
serialization.
it's mysterious, how the core lib handles this. also i'd love to
figure
out, why the php command (un)serialize fails with the cake session
data
field.
see this thread
http://groups.google.ch/group/cake-php/browse_thread/thread/706a27f513ea1a1c/
where i posted a pretty ugly function which (de)serializes the session
data field.
seems like this field is stored in a non-standard way.
hmmm. guess i need to have a closer look to the session lib.
j.
>
> I hope that makes sense, and I'm sure the people smarter than me
> around here (for there are many) will correct me.
>
> Preventing multiple logins is not an easy task to solve without a
> central location that is keeping track of who is logged in.
>
> --
> Chris Hartjes
>
> My motto for 2007: "Just build it, damnit!"
>
> rallyhat.com - digital photo scavenger hunt
> @TheBallpark -http://www.littlehart.net/attheballpark
> @TheKeyboard -http://www.littlehart.net/atthekeyboard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
