Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73000
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.160.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXa=QMn1QkSX7viuvPc4sQ7KkACsU+m6pLpn15JQScY9bw@mail.gmail.com>
References: <CAPhkiZxN3iJ8Xr1MwKxhsAYe1issjDYvccrkpBc8t9yupS9JCA@mail.gmail.com>
	<CAGa2bXa=QMn1QkSX7viuvPc4sQ7KkACsU+m6pLpn15JQScY9bw@mail.gmail.com>
Date: Sat, 8 Mar 2014 02:52:11 +0200
Message-ID: <CAPhkiZzSvffg-DZQrbC_eNCuTYi8OO2baS0C58JTFkMPbr46gg@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE] RFC: Introduce session_start() options -
 read_only, unsafe_lock, lazy_write and
From: narf@devilix.net (Andrey Andreev)

Hi Yasuo,

You're answering the wrong question. :)
What I asked is if the following example is possible:

    // start a session with cookie name 'foo'
    session_start(['name' => 'foo']);

Cheers,
Andrey.

On Sat, Mar 8, 2014 at 2:44 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Hi Andrey,
>
> On Fri, Mar 7, 2014 at 8:34 PM, Andrey Andreev <narf@devilix.net> wrote:
>>
>> Because this isn't really clear from the RFC ... can I assume that INI
>> options can also be passed to session_start()? Having only lazy_write,
>> read_only as options would be inconvenient. :)
>
>
> Many people don't like INI. (Although I love INIs :)
> Therefore, new options are allowed only as session_start() options.
>
> I don't mind at all having session.read_only=0 as default and users set it
> to session.read_only=1, then change it writable either
> ini_set('session.read_only', FALSE) or session_start(['read_only'=>FALSE]);
> as needed.
>
> I have to propose the change, though.
>
> Regards,
>
> --
> Yasuo Ohgaki
> yohgaki@ohgaki.net
>