Re: Session cache, lock and write

Hi Adam, On Fri, Nov 15, 2013 at 5:29 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote: > I wonder if a better approach would be to implement an improved files >> handler (under a different name) that had options for locking, caching >> and the like. Say it was called "awesome_files"[0]; you might have >> options like this: >> >> session.save_handler = awesome_files >> session.awesome_files.lock = On/Off >> >> I'd love to have a more flexible files handler, but I don't think we >> want to overspecialise the session implementation around it. > > > The behavior can be controlled by setting, so I would like to keep > single code files/mm/user and other save handlers. > > I don't mind creating new handlers too much, but I'm concerned for having > multiple settings for each save handlers. (e.g. Memcached/MongoDB save > handler have it own lock setting. It would be better to have single setting > for any save handlers that support it.) > It seems we need to think of new files save handler name. Perhaps, "files_ext"? Any better names? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net