Re: [RFC] Revert/extend/postpone original RFC about read_only, lazy_write sessions
| From: | Yasuo Ohgaki | Date: | Mon, 17 Mar 2014 09:02:06 +0000 |
| Subject: | Re: [RFC] Revert/extend/postpone original RFC about read_only, lazy_write sessions | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-73205@lists.php.net to get a copy of this message | ||
Hi Andrey,
On Mon, Mar 17, 2014 at 5:52 PM, Andrey Andreev <narf@devilix.net> wrote:
> > It updates time stamp always.
> >
> > It does
> >
> > "write data if data is updated"
> > or
> > "write data if save handler does not have update API"
> > or
> > "update time stamp if it is needed" (e.g. memcache does not need to
> update
> > time stamp since it updates time stamp by read. It's save handler
> > implementation choice what to do with update API)
> >
> > For save handlers like memcahe/memcached, session module is writing back
> the
> > same data just to waste resources when session data hasn't changed.
>
> And what about userland session handlers?
It's the same as C written module. Unless there is update() method, session
module
writes session data always.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net