Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73460 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43491 invoked from network); 28 Mar 2014 07:35:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Mar 2014 07:35:08 -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.52 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.52 mail-la0-f52.google.com Received: from [209.85.215.52] ([209.85.215.52:53617] helo=mail-la0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/D1-31219-82625335 for ; Fri, 28 Mar 2014 02:35:06 -0500 Received: by mail-la0-f52.google.com with SMTP id ec20so3441262lab.11 for ; Fri, 28 Mar 2014 00:35:02 -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=YqxSY7JWaYB8uuUzIlmPIgCdd2IV0P5M9XGKOh2V6eA=; b=P0GNPXIyLtk/B4pqMe/qV7/e4eEJ2xE387L+979CwblOiN2vTCgJQbDmTKrx9Jhglk 2YTx1pfviyM2vvuBkgPIMjzn+P5iZl7cEtPLDd2iIOE0pSIDhKSSxeVPgS+DwtNZh9k4 h0MtzswdRa7tqveYGicwg/NbkWG4hFs9/HlDB2L9sUSCvIYFI5wtCNRTvDcKQ3vG9xBu m0xdnIMHDpfYODWJFiLML1IMIxKlAK6xGsMNSOI5adt8tUYTlpLne60OGkspjBRFDDbY f2xqvy63Kgdv+SHYBFMnO4xOdj6Nd3ojqJJIb2lcL0IHBZ441X9zWcazGw+6y4reEg4k noGg== X-Received: by 10.112.205.35 with SMTP id ld3mr4237299lbc.1.1395992102157; Fri, 28 Mar 2014 00:35:02 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Fri, 28 Mar 2014 00:34:22 -0700 (PDT) In-Reply-To: References: <010e01cf4788$05f3c5a0$11db50e0$@devtemple.com> <01c801cf47c0$59acbf20$0d063d60$@devtemple.com> Date: Fri, 28 Mar 2014 16:34:22 +0900 X-Google-Sender-Auth: GpW9b27gJSIpNI6K6e_aA0K27bE Message-ID: To: Julien Pauli Cc: Andrey Andreev , Bill Salak , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c3d8645bc33e04f5a5bd7b Subject: Re: [PHP-DEV] [RFC] session_start(), read_only, lazy_write; Take 2 From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c3d8645bc33e04f5a5bd7b Content-Type: text/plain; charset=UTF-8 Hi Julien, On Wed, Mar 26, 2014 at 7:29 PM, Julien Pauli wrote: > > 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. I'm not sure if it's good to have "and" or not, but I'm OK with or without "and". Should I change it now? I mean in my github repo. I haven't committed the RFC patch yet. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c3d8645bc33e04f5a5bd7b--