Re: Session: More strict session data management
| From: | Yasuo Ohgaki | Date: | Sat, 31 Jan 2015 20:42:14 +0000 |
| Subject: | Re: Session: More strict session data management | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-81500@lists.php.net to get a copy of this message | ||
Hi all,
On Sun, Feb 1, 2015 at 5:30 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> On Sat, Jan 31, 2015 at 11:44 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>
>> As I described already, current session management is lazy to delete
>> obsolete
>> session data. New behavior is much stricter than now and there is no
>> exposed
>> internal data to users(script). The "hidden" timestamp only exists in
>> obsolete
>> session data. New behavior requires less GC also.
>>
>
> Current session manager is lazy for expiration also. The same method,
> "hidden"
> timestamp, can be used for housekeeping.
>
> If the timestamp is updated always, "lazy_write" option is spoiled. To
> prevent that,
> last modified time updates could be done with longer resolution, i.e.
> Update timestamp
> by every minute, not second.
>
> With this, GC is only need for true GC. i.e. GC will not be used to expire
> session data.
> Therefore, GC may be done once a day, for example.
>
> Any comment?
>
If there aren't comments, I shall start writing a RFC for this in a few
days.
Please comment, if you have.
Thank you.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net