|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2011-12-17 18:15 UTC] cataphract@php.net
-Status: Open
+Status: Duplicate
[2011-12-17 18:15 UTC] cataphract@php.net
[2012-01-04 01:16 UTC] arpad@php.net
[2012-01-04 01:18 UTC] arpad@php.net
-Status: Duplicate
+Status: To be documented
[2012-01-04 01:18 UTC] arpad@php.net
[2012-01-27 20:08 UTC] frozenfire@php.net
-Status: To be documented
+Status: Assigned
-Assigned To:
+Assigned To: frozenfire
[2012-01-27 22:08 UTC] frozenfire@php.net
[2012-01-27 22:11 UTC] frozenfire@php.net
-Status: Assigned
+Status: Closed
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sun Nov 02 04:00:02 2025 UTC |
Description: ------------ session_set_save_handler expects callbacks to session handler's operations (open, close, etc). It would be great if this function accepts a core's session handler interface. Something like: <?php interface Session_Handler_Interface { function open(); function close(); function read(); function write(); function destroy(); function gc(); } class Some_Handler implements Session_Handler_Interface { // implementations .... } $handler = new Some_Handler(); session_set_save_handler($handler); Then, we'll have an OOP approach too. The old one should not be removed. Thank you.