Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73443 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3385 invoked from network); 26 Mar 2014 10:30:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Mar 2014 10:30:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.179 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.220.179 mail-vc0-f179.google.com Received: from [209.85.220.179] ([209.85.220.179:52458] helo=mail-vc0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 39/70-33864-82CA2335 for ; Wed, 26 Mar 2014 05:30:01 -0500 Received: by mail-vc0-f179.google.com with SMTP id ij19so2092576vcb.24 for ; Wed, 26 Mar 2014 03:29:58 -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=gvVuv+ffkVtlMPv3BVUQTuu50HYw9FdU3S7NVVF89Gk=; b=g8EHh0J51o9A9yxVxdrfzZkI8mV1P113761gm3Gu3V3EqM5xiQtYhgCe9MCzKalEB8 nCJ4Vjq0lmGGKcxo0Orv/r2YO2TyJOctwmckdGM0Uvv6Kz+jMHw3nFdj07QhAKPpJFK0 /ldKeo6EUijMNEkkpNIgbY/LFz3cVValVPIAd+tFaevJy3fGpQfE8fUYfRb2US0DdcYR OZzBxBZFzkyyCCg0U8flgjEPPIrf55HrzbIdateDQ/9gJQoAAGseEMnmUUU1yiLuG4gb oGWeKykNEgDEFz3vw9P0t+zF+STjkGfMwhfTyTPUuzvtdnbUpihUoJxNktxK2hBa+FJ/ zOVw== X-Received: by 10.52.135.132 with SMTP id ps4mr18424337vdb.2.1395829797914; Wed, 26 Mar 2014 03:29:57 -0700 (PDT) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.220.81.68 with HTTP; Wed, 26 Mar 2014 03:29:16 -0700 (PDT) In-Reply-To: References: <010e01cf4788$05f3c5a0$11db50e0$@devtemple.com> <01c801cf47c0$59acbf20$0d063d60$@devtemple.com> Date: Wed, 26 Mar 2014 11:29:16 +0100 X-Google-Sender-Auth: IJQMLY3XtHVckkQQz9yGTpdHdtY Message-ID: To: Andrey Andreev Cc: Bill Salak , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=bcaec51a709a459c9204f57ff3a1 Subject: Re: [PHP-DEV] [RFC] session_start(), read_only, lazy_write; Take 2 From: jpauli@php.net (Julien Pauli) --bcaec51a709a459c9204f57ff3a1 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Mar 25, 2014 at 1:55 PM, Andrey Andreev wrote: > Hi, > > In order to avoid further arguments about whether a separate function > for read-and-close is better or not, I've added an alternative > proposal - to rename the option to 'read_close' or 'read_and_close'. > After all, the most important thing is that it's not 'read_only'. I agree "read_and_close" is much better discribing what it really does , so I prefer it. For non BC changes etc.. , please, consider that you'll have a big time for rethinking the whole session module for PHP6 if you want to (and I think I'll be part of deep discussions here) So don't bother too much in searching solutions for introducting new concepts in PHP5.X session module while keeping BC. Keep all those for PHP6. We are near 5.6 freeze, not that I dont want new shinny features, but what I want for 5.6 is something both consistent and voted, should it be "just a tiny feature". Work and thoughts are not lost anyway. Julien.P --bcaec51a709a459c9204f57ff3a1--