Req #77795 [Opn->Sus]: Suggestion: Create "phar" session.save_handler Option
Edit report at https://bugs.php.net/bug.php?id=77795&edit=1
ID: 77795
Updated by: cmb@php.net
Reported by: webmaster at RealityRipple dot com
Summary: Suggestion: Create "phar" session.save_handler
Option
-Status: Open
+Status: Suspended
Type: Feature/Change Request
Package: Session related
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
This feature request appears to be controversial, and as such
requires an RFC. If you're still interested in this feature,
please pursue the RFC process[1]. For the time being, I suspend
this ticket.
[1] <https://wiki.php.net/rfc/howto>
Previous Comments:
------------------------------------------------------------------------
[2019-03-26 10:27:47] webmaster at RealityRipple dot com
Description:
------------
While it is possible to write this by hand using session_set_save_handler or a plugin, it seems like
it would be a good idea to build-in saving sessions to a single PHAR Data file. The two technologies
would seem to compliment each other fairly well, and it would be helpful as far as file count
limitations go, which many shared hosting servers implement. It may also help to stimulate use of
PHAR files by developers in other, similar cases.
I have not set up any test environments to see what kind of speed or system usage issues may exist
from using PHAR so actively, but as long as the file isn't compressed, it shouldn't be too
bad.
It would, additionally, be of some use to re-purpose session.save_path to point to a file rather
than a directory. Whether to create a tar/zip option or detect it by file extension is up to you,
though I'd suggest creating a session.save_format or save_type or what have you, just in case a
user feels like using .sess or .tmp or some other unexpected file extension, or no extension at all.
Plus, you already have the 'Phar file format constants' defined. It may also be best to
require tar in all instances, if the performance is that superior to zip.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=77795&edit=1
Thread (2 messages)