Hi Cam, Thanks for your reaction. I was wondering if u could send me some example code maybe;-) I am a bit new to session based login systems myself;-) Thanks already.
Best regards, Davy Obdam, mailto:info@;davyobdam.com > David and Davy, > > My two bobs worth - I like to use sessions myself usually, I > suppose because it means my scripts are controlling access > rather than the server or the operating system. With sessons > you can store all sorts of variables such as exactly what the > user can do in a list of tasks rather than just "will we let > him in or not". The user submits a form with his username > and password, I look them up in a database, and if I find him > I grab a "task list" of things he is allowed to do on the > site (could be different for every user) and store them in a > session. Everytime he tries to go somewhere on the site the > script first checks if that task is in his list - > furthermore, you can kick him off if he has overstayed or > there has been no action for a period of time - also gives > you the opportunity to log or time his total activity on the site. > > I wrap each script in a small "include" routine which does > all this so its > no big deal in terms of coding effort or extra overhead. > You might like to > go this road rather than the simpler but more restrictive > HTTP auth. way. > > Cheers CD -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
