Re: Revert session_serializer_name(), session_gc()
| From: | Yasuo Ohgaki | Date: | Thu, 13 Mar 2014 01:40:07 +0000 |
| Subject: | Re: Revert session_serializer_name(), session_gc() | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-73093@lists.php.net to get a copy of this message | ||
Hi Andrey,
On Thu, Mar 13, 2014 at 8:43 AM, Andrey Andreev <narf@devilix.net> wrote:
> > I'll fix root cause of GC issue later. GC should not depend on luck.
>
> What do you mean you'll fix it? What would the solution to that be?
Save handler may keep & check last GC time. If it's over session.expire,
perform GC.
Issue is that "session data that should be deleted" is not deleted and
could be alive long term due to current design. Current design is good
enough for many usage, but it is not the best practice obviously.
"Keep & check last GC time" requires additional overhead for every request.
This is the reason why I prefer to have session_gc() and encourage users to
use it properly.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net