Hi all, On Sun, Feb 1, 2015 at 5:30 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote:
> On Sat, Jan 31, 2015 at 11:44 AM, Yasuo Ohgaki <yohg...@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 yohg...@ohgaki.net
