- From: Charles McCathieNevile <charles@sidar.org>
- Date: Thu, 31 Jul 2003 13:11:00 +0200
- To: "Lauke PH" <P.H.Lauke@salford.ac.uk>
- Cc: "Scarlett Julian \(ED\)" <Julian.Scarlett@sheffield.gov.uk>, <w3c-wai-ig@w3.org>
60 minutes is already a fair bit of time. If you had a second config file, and a variable referring to the relevant file, a user could select the "more time" version (just the same, but using the other config). Approaching this like a multilingual site - where you autogenerate a mirror version with more time - might be easy. Depends on your setup. And remember that in some cases there are real world constraints - it is simply not possible to let someone have 90 minutes between noon and 1pm, however much that may impact on their life. cheers Chaals On Thursday, Jul 31, 2003, at 12:53 Europe/Zurich, Lauke PH wrote: > >> Nice idea but I'm not sure how easy that would be in reality. >> For instance we're building a PHP intranet for schools and >> have specified the session time out as 60 minutes. It would >> quite easy to allow site administrators to change this but it >> would be a global change to a config file and would affect >> all users who logged in. > > Ok, I'm not sure if this would work, but...here goes: > how about setting the session time out quite high (1440 minutes) > and then set a specific time out for the session cookie > (see > <http://www.php.net/manual/en/function.session-set-cookie-params.php>) > depending on whether the user requires more time or not ? > There's probably a very fundamental flaw with this plan that > I'm overlooking (e.g. what happens when cookies can't be set, and > PHP dynamically adds the session ID to links etc), but maybe someone > more knowledgeable than me could fill in the gaps ? > > Patrick > ________________________________ > Patrick H. Lauke > Webmaster / University of Salford > http://www.salford.ac.uk > > -- Charles McCathieNevile Fundación Sidar charles@sidar.org http://www.sidar.org
Received on Thursday, 31 July 2003 07:11:54 UTC