Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79311
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
Message-ID: <df52d5d1e51c2ce8be90ac4d01989cd4.squirrel@webmail.klapt.com>
In-Reply-To: <5478FFB8.1090000@gmail.com>
References: <790a8d7299a7cda01ee76d8293b7d5af.squirrel@webmail.klapt.com>
    <5478FFB8.1090000@gmail.com>
Date: Sat, 29 Nov 2014 19:14:33 +0100
To: "Stanislav Malyshev" <smalyshev@gmail.com>
Cc: "Anatol Belski" <anatol.php@belski.net>,
 internals@lists.php.net
User-Agent: SquirrelMail/1.5.2 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Native TLS
From: anatol.php@belski.net ("Anatol Belski")

Hi Stas,

On Sat, November 29, 2014 00:05, Stanislav Malyshev wrote:
> Hi!
>
>
>> this is a long spoken topic which is now embodied in
>> https://wiki.php.net/rfc/native-tls . A preliminary implementation is
>> there as well, thus we can discuss it.
>
> This sounds great! \o/
> I understand there's no practical performance impact? If so, code
> simplification looks like a real win.
>
yep, the tests show it's at least as fast as the mainstream.

The patch from the first RFC was replacing the array access with offset
logic. Unfortunately I had to revert it as it was playing not good with
the current master, so I just separated it from the approach. I see the
"index vs offset" as something one can build upon the current RFC.

Regards

Anatol