Re: [VOTE] RFC: Introduce session_start() options - read_only, unsafe_lock, lazy_write and
| From: | Andrey Andreev | Date: | Sat, 08 Mar 2014 00:52:11 +0000 |
| Subject: | Re: [VOTE] RFC: Introduce session_start() options - read_only, unsafe_lock, lazy_write and | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-73000@lists.php.net to get a copy of this message | ||
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
>