"Yasuo Ohgaki" wrote in message
news:caga2bxyax05jbjavyxfsjyy6xia+4u14npfgywscl4aoofq...@mail.gmail.com...
Hi Marco,
Thank you for explaining the reason why!
On Mon, Dec 5, 2016 at 11:12 AM, Marco Pivetta <ocram...@gmail.com> wrote:
I voted "no" because I don't see any advantage over using a custom
session
save handler, besides adding more API that partially covers custom
session
save handlers.
You mean current OO custom save handler, I suppose.
Firstly, current OO custom save handler design (use of previously used
internal save handler as its base class) is not good. Overriding
open()/close()/etc are useless, moreover harmful. Number of bugs
proved it is not good.
I have been using session_set_save_handler() since 2002 to store all session
data in a database, and I have never encountered any problems. Why is it
"not good"? What bugs are there?
I do not see the point in this RFC.
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
