Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81500 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60404 invoked from network); 31 Jan 2015 20:42:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jan 2015 20:42:58 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.49 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.49 mail-qg0-f49.google.com Received: from [209.85.192.49] ([209.85.192.49:54215] helo=mail-qg0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/23-39884-15E3DC45 for ; Sat, 31 Jan 2015 15:42:58 -0500 Received: by mail-qg0-f49.google.com with SMTP id i50so42793570qgf.8 for ; Sat, 31 Jan 2015 12:42:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=xNXOl7zFNPx7Mj5F8jVRClvJadFPMArbHSJ8CcxZL/I=; b=DzHBxnwMpfHwXrJF1VV1GJ10xRT2lSTWsc2ahCJLXkWUMqYIec1F0citPnMbrFwqGJ MdbjddZBbtVr3rKJYiVRENyHteyQz6fIwXL86J1sltmu4Y4Zar69jKtcgGMJM3lNU0zC V8KKFawF92I5WwJd5OXd/Hv6aV9z/4curvspC3GvQRIcWLopgdrvp39eKTnbbK8ovNJ0 R3PTq5/ArL83czJxsei0YTV78uQ8i1/P9fBMEdtRGFgRQbx4guZrM/OPaVifjMW8oZA0 6kiI8txzfOtAXq7OZk2a/dMX9HChde/NbjKbSyVa3ALW3dQFceVTBJ/LiT7Up3Tm5VbI TKYw== X-Received: by 10.224.111.194 with SMTP id t2mr25066709qap.86.1422736974866; Sat, 31 Jan 2015 12:42:54 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.93.70 with HTTP; Sat, 31 Jan 2015 12:42:14 -0800 (PST) In-Reply-To: References: Date: Sun, 1 Feb 2015 05:42:14 +0900 X-Google-Sender-Auth: OVwPN3sLLJHzKyuu8U5nTZ6FiBU Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7b604582fef20e050df8c336 Subject: Re: Session: More strict session data management From: yohgaki@ohgaki.net (Yasuo Ohgaki) --047d7b604582fef20e050df8c336 Content-Type: text/plain; charset=UTF-8 Hi all, On Sun, Feb 1, 2015 at 5:30 AM, Yasuo Ohgaki wrote: > On Sat, Jan 31, 2015 at 11:44 AM, Yasuo Ohgaki wrote: > >> As I described already, current session management is lazy to delete >> obsolete >> session data. New behavior is much stricter than now and there is no >> exposed >> internal data to users(script). The "hidden" timestamp only exists in >> obsolete >> session data. New behavior requires less GC also. >> > > Current session manager is lazy for expiration also. The same method, > "hidden" > timestamp, can be used for housekeeping. > > If the timestamp is updated always, "lazy_write" option is spoiled. To > prevent that, > last modified time updates could be done with longer resolution, i.e. > Update timestamp > by every minute, not second. > > With this, GC is only need for true GC. i.e. GC will not be used to expire > session data. > Therefore, GC may be done once a day, for example. > > Any comment? > If there aren't comments, I shall start writing a RFC for this in a few days. Please comment, if you have. Thank you. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --047d7b604582fef20e050df8c336--