Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73200 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50098 invoked from network); 17 Mar 2014 00:10:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Mar 2014 00:10:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.43 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.43 mail-la0-f43.google.com Received: from [209.85.215.43] ([209.85.215.43:51046] helo=mail-la0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/93-20890-95D36235 for ; Sun, 16 Mar 2014 19:10:02 -0500 Received: by mail-la0-f43.google.com with SMTP id e16so3203321lan.16 for ; Sun, 16 Mar 2014 17:09:59 -0700 (PDT) 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:cc:content-type; bh=eSc51lEKOmIDzaiozBYZNQlSv+MlQ/fYVWfutmlD3UA=; b=uEkqmKax6cXq/l5UoO2Bpo9r3jBAuxivUVsH6IzzVIkfAAGMsRd4xFkQX04Ft/nfNL LzEaY+yd5WIYU6zm1Aod4K2ouKjzS5ZOwykUQTzdmjm65DzIRI628HjLAVd7uijs6S5a 5aPwmxrg+PfVXgX0kmX7qEvJHQuMvu1NRdGOq9WLj/gndlgjbijDMm8FGRVFi39JHD/j RLVkZyOGF+FXxL7D/gFRBEJ3l7iAwswXCtwZcN9Xv03pfrqQ8xoyl0rk42Kmq4O9FBe0 IU8Ohf5RiG30dfVq/2zAf/LcC+pVy8MRTkx1rwSZt8+Vv9+fPzp2cgWppV5c/mRdSyNM VqBA== X-Received: by 10.152.246.43 with SMTP id xt11mr86188lac.34.1395014999253; Sun, 16 Mar 2014 17:09:59 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Sun, 16 Mar 2014 17:09:19 -0700 (PDT) In-Reply-To: References: <5324FE40.1070704@sugarcrm.com> <532603A0.8060802@sugarcrm.com> Date: Mon, 17 Mar 2014 09:09:19 +0900 X-Google-Sender-Auth: vn9kMCM6Auef_Hi470uHHqwjNwo Message-ID: To: Andrey Andreev Cc: Stas Malyshev , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1133a7747ca87d04f4c23ddf Subject: Re: [PHP-DEV] [RFC] Revert/extend/postpone original RFC about read_only, lazy_write sessions From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a1133a7747ca87d04f4c23ddf Content-Type: text/plain; charset=UTF-8 Hi Andrey, On Mon, Mar 17, 2014 at 8:07 AM, Andrey Andreev wrote: > >> "last used", "last updated", "last modified", "last accessed" ... > >> however you call it, it always exists in some form. Without such a > > > > Last used and last modified are very different things. Nothing prevents > > one from tracking either. We need to check it is done properly and is > > compatible with old handlers, but it should be entirely possible to do > > it in a BC way. > > See, this is what I meant with 'read_only' it may be a name closely > explaining what it does, but in fact it has an essentially different > meaning. :) The session module only uses one of those timestamps is > what I meant here. And it may be possible to handle that in a BC way, > but the RFC doesn't mention if that's really the case and/or how it > could be done - this is stuff that must be addressed. It updates time stamp always. It does "write data if data is updated" or "write data if save handler does not have update API" or "update time stamp if it is needed" (e.g. memcache does not need to update time stamp since it updates time stamp by read. It's save handler implementation choice what to do with update API) For save handlers like memcahe/memcached, session module is writing back the same data just to waste resources when session data hasn't changed. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a1133a7747ca87d04f4c23ddf--