> What is the point of having a unique ID for each session if the only > thing that matters is the data stored within it? Why have a session id > at all if it can't be used to uniquely track a user?
Well, it can, and it does. I guess it's all in how you use it. If my session id is "abcd", then when I log out, your program should erase all of the data in the session and forget that it ever knew about a session called "abcd". That way, even if I log in with the same session (since the cookie wasn't deleted, probably, which is probably the cause of this whole problem), then I will be a new user and not related to the old user/session in any matter. > p.s. I'm new to this list as you may have noticed and so far this is the > only list that I've been on that doesn't use the list's address as the > return address. Do I have to manually put it in the To box each time? Yeah, the topic of discussion quite a bit in the past few days. Just use the Reply-All button, please. ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
