HI all, On Thu, Nov 6, 2014 at 6:30 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote:
> On Wed, Nov 5, 2014 at 10:54 AM, Damian Wadley <p...@requinix.net> wrote: > >> Apparently this caused >> problems for some people as they made 68331 a few days ago. >> > > Just a quick note for this. The user would like to access session > data(session handler) > regardless of data modification. I suppose it could be solved if session > has user space > "update" handler as I suggested originally. > > Alternatively, session_write_close()/session_commit() may be changed, so > that it > is called unconditionally during shutdown. I have to read the code to be > sure if this is possible. > > BTW, anyone know the reason why the user need to call > session_write_close()/session_commit() > unconditionally? Accounting, perhaps? > The issue user has reported could be solved easily by calling write API during shutdown, IIRC. An explicit flag for this might be needed. I'm just curious for what reason the user needs to call session_write_close() during shutdown. It could be used as user states in old PHP, but it does not make it valid usage/design automatically, so I wander the reason. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
