Re: Re: Revert session_serializer_name(), session_gc()

From: Date: Sat, 15 Mar 2014 04:36:05 +0000
Subject: Re: Re: Revert session_serializer_name(), session_gc()
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hi all,

On Sat, Mar 15, 2014 at 1:15 PM, Yasuo Ohgaki <[email protected]> wrote:

>
>> Now back to the main topic:
>>
>> Please exclude session_serializer_name(), session_gc(),
>> session_reset(), session_abort() and the "session write short-circuit"
>> from the 5.6 branch.
>>
>
> I removed session_serializer_name() and session_gc()
> (Although session_gc() is mandatory API, IMO)
> I like the idea removing INI modifying function in the future release.
>
> I don't understand reason why you insist removal of session_reset()
> and session_abort(). They are just missing API for session module,
> like session_gc().
>
> There should be API (i.e. function/method or parameters) for distinct
> operations that user may use.
>
> I may agree if you could provide the reason why there should not be
> these APIs.
>

I thought it might be better to explain what new functions do.

session_gc() executes GC without tweaking INIs.
session_abort() aborts session without writing $_SESSION. There is no way
achieve w/o it.
session_reset() re-reads session and re-initializes $_SESSION. There is no
way achieve w/o it. (It could be done with session_abort(), though)
"write short circuit" omits "write" when $_SESSION hasn't change. There is
no point calling write API and writing to storage for the same data.

Regards,

--
Yasuo Ohgaki
[email protected]


Thread (41 messages)

« previous php.internals (#73174) next »