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

From: Date: Thu, 13 Mar 2014 22:18:48 +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  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hi Andrey,

On Fri, Mar 14, 2014 at 6:01 AM, Andrey Andreev <[email protected]> wrote:

> All I'm saying is, this whole thing wasn't handled properly and/or
> with the required attention.
> It's nobody's fault, but it ended up broken and I want to fix it
> (possibly with the help of somebody to write the patch, because I'm
> not a C programmer).
>

I think shared lock is useful. It requires additional work to change save
handler interface and save handler code. It's a distinct feature from
read_only. You can get status via session_status() if you need to know
during execution. i.e. If session is started with read_only, you'll
get PHP_SESSION_NONE status.

I suppose read_only is good enough name for the feature. I appreciate
better name for it, if there is.

Although I would not like to propose/implement the RFC now, but I may
implement it if RFC passes.

Regards,

--
Yasuo Ohgaki
[email protected]


Thread (41 messages)

« previous php.internals (#73133) next »