Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81480 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12925 invoked from network); 31 Jan 2015 11:12:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jan 2015 11:12:18 -0000 Authentication-Results: pb1.pair.com header.from=bas@tobin.nl; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=bas@tobin.nl; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain tobin.nl designates 208.97.132.208 as permitted sender) X-PHP-List-Original-Sender: bas@tobin.nl X-Host-Fingerprint: 208.97.132.208 homie.mail.dreamhost.com Linux 2.6 Received: from [208.97.132.208] ([208.97.132.208:58642] helo=homiemail-a61.g.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/02-01805-098BCC45 for ; Sat, 31 Jan 2015 06:12:17 -0500 Received: from homiemail-a61.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a61.g.dreamhost.com (Postfix) with ESMTP id C3474578059; Sat, 31 Jan 2015 03:12:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=tobin.nl; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=tobin.nl; bh=FqT6twBu6ura33ZGSZR9cCzk/8o=; b=Rb8XBqSc3agsUQiM0mKuYFHKUOEu qepsFKp6eHwQWmZ4Tm4Tjgy5ZrzLrl0P4yDF86W3p+RMjT1rJi89KHiZ6D5DbxnL b3J471xGFXszSK+flmsOhC8u4t8zLrbzhO20NlyLVtEaLo8N9TFd5qQf6XqKrVLK H9RAstqPKdvn8so= Received: from [192.168.1.21] (84-53-89-40.adsl.unet.nl [84.53.89.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bas@tobin.nl) by homiemail-a61.g.dreamhost.com (Postfix) with ESMTPSA id 4CB8D57807B; Sat, 31 Jan 2015 03:12:13 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) In-Reply-To: Date: Sat, 31 Jan 2015 12:12:10 +0100 Cc: "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <46440117-42C7-40DD-8504-4EE938385050@tobin.nl> References: To: Markus Amalthea Magnuson X-Mailer: Apple Mail (2.2070.6) Subject: Re: [PHP-DEV] Why does session.gc_maxlifetime default to 1440 seconds? From: bas@tobin.nl (Bas van Beek) Well the number 1440 itself is not so arbitrary as it's the amount of = minutes in a day. Maybe that's why the number popped up. In the end 24 minutes does seem to be fine for the majority of people = and with people that care about session duration it's really easy to = update :) > Op 31 jan. 2015, om 11:45 heeft Markus Amalthea Magnuson = het volgende geschreven: >=20 > Hey Yasuo, >=20 > Yes, there can surely be no other reason for the existence of the = value, > than that someone wrote it :) >=20 > I think what I'm interested in is the reasoning behind it, since it = seems > so arbitrary. It's not 20 or 30 minuts, for example. >=20 > I have tried emailing the author a long time ago but never received a = reply. >=20 > On Sat, Jan 31, 2015 at 12:54 AM, Yasuo Ohgaki = wrote: >=20 >> Hi Markus, >>=20 >> On Sat, Jan 31, 2015 at 4:02 AM, Markus Amalthea Magnuson < >> markus.magnuson@gmail.com> wrote: >>=20 >>> I've been trying to figure out the design decision behind why the = default >>> value of session.gc_maxlifetime is 1440 seconds (24 minutes)? >>>=20 >>> Does anyone know or have any good sources? >>>=20 >>=20 >> Because the author set this value, I think. >> It was 1440 since session module is introduced, IIRC. >>=20 >> I think 1440 is reasonable value for many applications. >>=20 >> Regards, >>=20 >> -- >> Yasuo Ohgaki >> yohgaki@ohgaki.net >>=20