Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73205 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81463 invoked from network); 17 Mar 2014 09:02:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Mar 2014 09:02:50 -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.215.50 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.50 mail-la0-f50.google.com Received: from [209.85.215.50] ([209.85.215.50:43819] helo=mail-la0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 05/91-06931-93AB6235 for ; Mon, 17 Mar 2014 04:02:50 -0500 Received: by mail-la0-f50.google.com with SMTP id y1so3383614lam.23 for ; Mon, 17 Mar 2014 02:02:46 -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=QWomd8YuE/nuFFAZwayfsdUgLgJMi8i0m7zStcnergw=; b=wwX3jiJlI/2bO6vGj4nWe/JokDJ5hR1ZQhsi8y2BRZuQJmJaCvW/LLcxZ1RS0+HU8C ZcBlHRt/1m8lyhGmUHYYg0C/SHnjBquPXTQHVWEjWDcreI0GHgPZS3J7x3GK4n8XK5QK aLIuhFwCB+sx+FEE6jBl/25PXvOCr8J+MsxfgzyfkHNn6b8GB4XOi4zu9UqOnQR2AJu+ nh9XBHVEfZnhc4KxsQWABJLiakUgFgcoJDNPK61FWQ4EjOCv9lsYXzmo/r6pA/xl1e3s 6G71J3zMmfSBWZ4O8sA3mKR47KLEiTmTfABP+ZTn/5/IrnhdVopXWyiaF2KuQysfQJEM P91w== X-Received: by 10.112.125.225 with SMTP id mt1mr787246lbb.35.1395046966482; Mon, 17 Mar 2014 02:02:46 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Mon, 17 Mar 2014 02:02:06 -0700 (PDT) In-Reply-To: References: <5324FE40.1070704@sugarcrm.com> <532603A0.8060802@sugarcrm.com> Date: Mon, 17 Mar 2014 18:02:06 +0900 X-Google-Sender-Auth: M-M3sDo9z4861hZwh19p9cbcmVc Message-ID: To: Andrey Andreev Cc: Stas Malyshev , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0112bfb8e1dca104f4c9ae7b Subject: Re: [PHP-DEV] [RFC] Revert/extend/postpone original RFC about read_only, lazy_write sessions From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0112bfb8e1dca104f4c9ae7b Content-Type: text/plain; charset=UTF-8 Hi Andrey, On Mon, Mar 17, 2014 at 5:52 PM, Andrey Andreev wrote: > > 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. > > And what about userland session handlers? It's the same as C written module. Unless there is update() method, session module writes session data always. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0112bfb8e1dca104f4c9ae7b--