Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78783 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77368 invoked from network); 6 Nov 2014 06:28:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2014 06:28:09 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.41 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.218.41 mail-oi0-f41.google.com Received: from [209.85.218.41] ([209.85.218.41:38417] helo=mail-oi0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F1/A8-28384-6F41B545 for ; Thu, 06 Nov 2014 01:28:06 -0500 Received: by mail-oi0-f41.google.com with SMTP id e131so302986oig.14 for ; Wed, 05 Nov 2014 22:28:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BjxZB4hBw6reyk88gQclbsuQBmx22UZfXtzLah2BpYs=; b=PCj7mbbhSZ4SvYKtAZe0HgOwPp/3mt1pYnJyMNzoqXsvTDLnSmUdGXLsRKBbFSEc6D wjVQ5n5F4lQohXf3j+wJeZloRldr0G83N0hzUS29MLfEnPWraAbMJyJ61gGkB3NYiCPj jDJ0+WOThz0EQ/rSeY/4CEXYkF+HWOnSOR/uXtLW1yxMPUCLfc4CuQbHE+FMgnvJb9+w 1FZDIav4ef1KoCbF3N1wiAEhWfb2Jl3ft4MpBNp1E0nRPvdVVJ/nyKMCNQyTWm6ArlEY HO3jM51/PgMYZ8ucG7ynKevyEb2lkpextzbQ6YpSuD4uQCh3Vo8s4fv0TkCEaQcJ4bTt tozA== MIME-Version: 1.0 X-Received: by 10.202.63.137 with SMTP id m131mr302361oia.75.1415255283248; Wed, 05 Nov 2014 22:28:03 -0800 (PST) Received: by 10.60.116.39 with HTTP; Wed, 5 Nov 2014 22:28:03 -0800 (PST) Received: by 10.60.116.39 with HTTP; Wed, 5 Nov 2014 22:28:03 -0800 (PST) In-Reply-To: References: Date: Thu, 6 Nov 2014 07:28:03 +0100 Message-ID: To: Yasuo Ohgaki Cc: PHP Internals , Andrey Andreev Content-Type: multipart/alternative; boundary=001a113dd4a46cb7c005072accaf Subject: Re: [PHP-DEV] PHP RFC: Introduce session_start() options - read_only, unsafe_lock, lazy_write and lazy_destroy From: tyra3l@gmail.com (Ferenc Kovacs) --001a113dd4a46cb7c005072accaf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2014.11.06. 7:10 ezt =C3=ADrta ("Yasuo Ohgaki" ): > > Hi all, > > The RFC https://wiki.php.net/rfc/session-lock-ini was accepted and the > patch for this was ready to merge, but it wasn't merged to 5.6 by mistake= . > > The patch is this. > https://github.com/yohgaki/php-src/compare/PHP-5.6-rfc-session-lock > (It's been a while and it has to be updated for current code) > > I may update the patch and merge, but question is which branch should be, > 5.6.3, 5.6.4, or master? > > I need comments from RM. > Thank you. > > -- > Yasuo Ohgaki > yohgaki@ohgaki.net As I mentioned in my mail yesterday, I would prefer delaying this for the next minor/major version (and reverting the write short circuit from 5.6). But putting that aside, I think it would make sense addressing the points brought up by Andrej regarding this rfc. Ps: and dont forget/ignore that originally only the read only/lazy write parts were accepted, the other two proposals did not. --001a113dd4a46cb7c005072accaf--