If you are at the mercy of your ISP (He controls the session life time setting), and you are not happy with the timelimit he has chosen, you can override it by adding your own session processing routines. http://us2.php.net/manual/en/function.session-set-save-handler.php You can hard code the session life for the garbage cleanup routine, in your handler routines, particularly if you use your own database table for saving session data (there are lots of good books out there that describe how using mysql). I've even set up different applications with different session life span, using different mysql tables for each app (and different routines, of course). Warren Vail -----Original Message----- From: Dale D. Attree [mailto:Dale.Attree@xxxxxxxxxxxx] Sent: Wednesday, July 05, 2006 10:58 PM To: Martin Staiger; php-windows@xxxxxxxxxxxxx Subject: RE: single sign on Make use of cookies and set the expiry of the cookie to equal 8 hours. In theory, this should create a cookie every day, therefore the user will only require to logon once a day. -----Original Message----- From: Martin Staiger [mailto:mstaiger@xxxxxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, July 05, 2006 8:34 PM To: php-windows@xxxxxxxxxxxxx Subject: single sign on dear group, how can we find out, if a user has a valid session on his windows client? We would like to use this session to authenticate in our web-application. Will we need active-x controls? Thanks, Marc -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
