Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73279 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13293 invoked from network); 18 Mar 2014 23:27:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Mar 2014 23:27:37 -0000 Authentication-Results: pb1.pair.com header.from=narf@devilix.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=narf@devilix.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.160.169 as permitted sender) X-PHP-List-Original-Sender: narf@devilix.net X-Host-Fingerprint: 209.85.160.169 mail-yk0-f169.google.com Received: from [209.85.160.169] ([209.85.160.169:53277] helo=mail-yk0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/B6-16983-766D8235 for ; Tue, 18 Mar 2014 18:27:37 -0500 Received: by mail-yk0-f169.google.com with SMTP id 142so21069468ykq.0 for ; Tue, 18 Mar 2014 16:27:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devilix.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5qMOc6NMckPuVIdHCvh7+qDnLiJTEEy7D/QgHyuiqT4=; b=jGT3spgdQ0/6twCg3GjbOY9hih1XsRTgNiqSHaursQKfwJo0Hx00u6MsFRdIPJAG2+ V5TpuYJQO1EUxnmm4JQDFxthQmZvLgoIlpVHXuyBB/TiTYK4DPyula2zUiivlpxjua5r PMM5N6wwqd7Iqmjjz0XgXbJwip2dBSBzsPbfw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=5qMOc6NMckPuVIdHCvh7+qDnLiJTEEy7D/QgHyuiqT4=; b=Fo0epzELl5pLV2oWLRzCCDev7I7uao5LFyrmt1+z3nXD5PvEGZ979ue0qnNsFqJ80d Gyd7nxeCZhzfSv2epn5+S0Mwwpg9qELxNOf8uUDFddlqnYYcRAfnzHKzcwhOqRshiiwk XzbXTyvoMkkhdxiiwUjNzXSHfAuPj9bXeCdBkzrtiim7Hee2IXR5fxlzcR39JEADlYAu W+XVAqGh7SczJs21Axi4ItQCK6Hei2Sh0qBGFcMxhCQD1Hytq5ALwbiB5TpHXTjsVtn0 Rym/RZuI2Lb73TyodD9ZSdUmV4BHxH0i+8UubRHPsRej5Wu/+XRyBtZuDnTODyzPzYzq Di2Q== X-Gm-Message-State: ALoCoQkaz0SnTmpRuQiXnvnWCO1gcHpWDVPs/i2jepiJjBMHYG+UelPDf3eSH5Ir4bBOZ9y+zPwk MIME-Version: 1.0 X-Received: by 10.236.172.33 with SMTP id s21mr45737100yhl.71.1395185253133; Tue, 18 Mar 2014 16:27:33 -0700 (PDT) Received: by 10.170.188.139 with HTTP; Tue, 18 Mar 2014 16:27:33 -0700 (PDT) In-Reply-To: References: <5324FE40.1070704@sugarcrm.com> <532603A0.8060802@sugarcrm.com> <5327DD6E.6030402@sugarcrm.com> Date: Wed, 19 Mar 2014 01:27:33 +0200 Message-ID: To: Yasuo Ohgaki Cc: Stas Malyshev , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Revert/extend/postpone original RFC about read_only, lazy_write sessions From: narf@devilix.net (Andrey Andreev) On Wed, Mar 19, 2014 at 1:04 AM, Yasuo Ohgaki wrote: > Hi all, > > On Tue, Mar 18, 2014 at 7:58 PM, Andrey Andreev wrote: >> >> Exacly why I wrote an RFC, except Yasuo already explained that current >> workflows (speaking of userland handlers) are not affected and BC is >> maintaned. > > > I found issue with object based save handlers, but it was solved without any > BC. > > I also added createSid() method support. If both create_sid() and > createSid() exists, > createSid() is used. I thought this was currently in discussion, and in a separate thread? >> > How about making it a INI option? It makes session_start() option >> > handling >> > code >> > a little simpler. It's not mandatory, though. >> >> +1 from me, if it is to be kept as an option. > > > I'm about to modify patch to make it INI. No objections for this? Well, I said 'if' we keep it as an option at all. I'd rather update the RFC to propose it as non-optional behavior since there are no downsides from it, as I understand. >> > I think we are better to have another SessionHandler object that support >> > new >> > APIs. >> > We can handle create_sid() method rename with new object also. We may >> > keep >> > current implementation undocumented and may document it new one >> > (createSid()) only. >> > I will name it "SessionUpdateTimestampHandler". If anyone has >> > suggestions, >> > I would appreciate it. >> >> I object, although it should've been called SessionFilesHandler in the >> first place, that way we could also have SessionMemcacheHandler, >> SessionWhateverHandler - way nicer than it currently is, but again - >> not the point of this discussion. > > > I removed new object. It's not needed anymore, since I prevented bogus > methods > registration. Bogus methods? I wrote this RFC because it was completely unclear how certain situations would be handled ... now this is also unclear. :) I sent you a private e-mail earlier today, perhaps you could explain me that in a reply to it so that we don't spam the list. Cheers, Andrey.