Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73104 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29366 invoked from network); 13 Mar 2014 10:03:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2014 10:03:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:51891] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8B/C2-12560-A6281235 for ; Thu, 13 Mar 2014 05:03:22 -0500 Received: (qmail 10340 invoked by uid 89); 13 Mar 2014 10:03:18 -0000 Received: by simscan 1.3.1 ppid: 10322, pid: 10336, t: 0.0689s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 13 Mar 2014 10:03:18 -0000 Message-ID: <53218295.9080903@lsces.co.uk> Date: Thu, 13 Mar 2014 10:04:05 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Revert session_serializer_name(), session_gc() From: lester@lsces.co.uk (Lester Caine) Patrick Schaaf wrote: > This way there is no longer any correctness problem, and a GC is only > needed to clean up sessions that are never requested again - and for that I > fully agree that a separate - e.g. cron driven - "GC now" job would be best > (not affecting latency of running frontent requests too much). I've not had much interest in this discussion as I am more than happy with how things work now. It is not unusual for my 'client' sessions to last for an hour or so without activity and their 'automatically' logging out was the problem originally. So now I'm set never to clear session data and run a clear up on the session directory before the site starts work in the morning. There are reasons a system wide approach may be more practical than changing how a single session handles things? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk