Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97009
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.155 cause and error)
To: internals@lists.php.net
References: <CAGa2bXbQaVe+LYM1u3Rofz-2MajC8=b_tjmYsVnFNS2bDFBzoQ@mail.gmail.com>
Message-ID: <507c801d-1442-c6c6-581c-16ced9d35a53@fischer.name>
Date: Sat, 19 Nov 2016 01:02:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAGa2bXbQaVe+LYM1u3Rofz-2MajC8=b_tjmYsVnFNS2bDFBzoQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  Hello, On 17.11.2016 11:55, Yasuo Ohgaki wrote: > > Session
    module implements serialize handler as module. > This RFC is to expose it
    to user space. > > RFC > https://wiki.php.net/rfc/user_defined_session_serializer
    > > PR > https://github.com/php/php-src/pull/2205 > > Comments are appreciated!
    [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
Subject: Re: [PHP-DEV] [RFC DISCUSSION] User defined session serializer
From: markus@fischer.name (Markus Fischer)

Hello,

On 17.11.2016 11:55, Yasuo Ohgaki wrote:
> 
> Session module implements serialize handler as module.
> This RFC is to expose it to user space.
> 
> RFC
> https://wiki.php.net/rfc/user_defined_session_serializer
> 
> PR
> https://github.com/php/php-src/pull/2205
> 
> Comments are appreciated!

Well, I like it. It's sometimes necessary to share session state with
non-PHP application and this is IMHO a welcome addition to ease the
exchange.

Btw, what is the proper way to signal a problem during
serialization/unserialization? I couldn't figure it out from the RFC nor
the PR and there doesn't seem to be a test case for it.
Return null/false? Throw an exception?

thanks,
- Markus