Re: [RFC] session_start(), read_only, lazy_write; Take 2
| From: | Julien Pauli | Date: | Fri, 28 Mar 2014 09:26:46 +0000 |
| Subject: | Re: [RFC] session_start(), read_only, lazy_write; Take 2 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-73465@lists.php.net to get a copy of this message | ||
On Fri, Mar 28, 2014 at 10:19 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Hi Julien,
>
> On Fri, Mar 28, 2014 at 6:15 PM, Julien Pauli <jpauli@php.net> wrote:
>
>> Yes please.
>>
>> Also, for error raising, I saw your github discussion.
>> We already raise errors in session functions when the session state is
>> not the good one at some point.
>> I suggest we do it as well for new session functions that's been
>> introduced : session_reset() and session_abort().
>> Leave session_write_close() as it is.
>>
>
> OK. I'll update my github soon.
> When you think it's ready to merge, please let me know or please merge it.
>
I'd like we finish the debatte for those two functions (session_abort() and
session_reset()). Those functions have not been RFC'ed from what I know.
And Andrey.A seems not to agree very well with them, or at least
session_reset().
As soon as debatte is finished, and we found a solution, then we'll merge
the ideas.
All other stuff should be done under RFC. Session module is critical, and I
would not want we merge badness or wrong stuff to 5.6 about it. If done, we
will revert anyway to have a stable API for the upcoming 5.6
All other ideas should go to 6.0 branch (to be branched soon).
Thx.
Julien