Re: [RFC] Object oriented session handlers
| From: | Mike Willbanks | Date: | Mon, 06 Jun 2011 17:00:51 +0000 |
| Subject: | Re: [RFC] Object oriented session handlers | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-53053@lists.php.net to get a copy of this message | ||
Forgot to keep the list on this one.
On Mon, Jun 6, 2011 at 11:19 AM, Mike Willbanks <pencap@gmail.com> wrote:
> A while ago I submitted a patch to allow session_set_save_handler() to
>> accept a class, and support the inheritance of the default session
>> handler's methods.
>>
>> The RFC has a more detailed description and the current patch:
>> https://wiki.php.net/rfc/session-oo
>>
>> Changes since this was last discussed:
>> - More sanity checking to prevent handlers being called in unexpected
>> states
>> - ZTS fixes
>>
>> Any thoughts?
>>
>
> Unfortunately the class may cause a BC break due to the naming. Although
> namespaces could help in reducing the potential scope of a BC break.
>
> This is a huge win for those of us with generally highly custom session
> handlers. This has been a consistent point of pain and being able to
> "extend" rather than reimplement would be a very nice enhancement.
>
> Now on the new SessionHandler object; is this now utilized by default? I
> seen the wrapper in the patch but it seems like we utilize all of the
> existing code with modifications to also utilize an object? Should
> the procedural way be deprecated at some point or is the plan to support
> both styles?
>
> Regards,
>
> Mike
>
>