Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
| From: | Yasuo Ohgaki | Date: | Thu, 30 Jan 2014 07:26:50 +0000 |
| Subject: | Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-71783@lists.php.net to get a copy of this message | ||
Stas,
On Thu, Jan 30, 2014 at 4:16 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
> > This is informational function for programmers, not for programs.
> > It requires active session to be useful because it needs active save
> handler
> > module. It's rather suitable as phpinfo(), but it might not be useful
> > for users.
>
> I'd say it's better to leave this for the docs. If you write session
> handler, you document what it's supporting and what's not and that would
> be much easier to read than call a function and also much clearer -
> there you can describe what works and what not in detail.
No problem. I think it's dirty also :)
Let leave it to docs. It will be removed from code and RFC.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net