Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98457 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32572 invoked from network); 9 Mar 2017 17:26:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Mar 2017 17:26:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=flaupretre@free.fr; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=flaupretre@free.fr; sender-id=unknown Received-SPF: error (pb1.pair.com: domain free.fr from 212.27.42.4 cause and error) X-PHP-List-Original-Sender: flaupretre@free.fr X-Host-Fingerprint: 212.27.42.4 smtp4-g21.free.fr Received: from [212.27.42.4] ([212.27.42.4:49565] helo=smtp4-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/10-31244-64091C85 for ; Thu, 09 Mar 2017 12:26:30 -0500 Received: from [172.16.0.28] (unknown [158.255.108.131]) (Authenticated sender: flaupretre) by smtp4-g21.free.fr (Postfix) with ESMTPSA id 8D83919F4B5 for ; Thu, 9 Mar 2017 18:26:26 +0100 (CET) To: PHP internals Message-ID: <8509e280-b58b-d5a9-8e12-25665f55d2c2@free.fr> Date: Thu, 9 Mar 2017 18:26:26 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Proposing a new 'cache_key' streams operation From: flaupretre@free.fr (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Hi, PR is : https://github.com/php/php-src/pull/1711 This PR creates a mechanism to be used by opcode caches to determine whether a stream-wrapped URI is cacheable, and the key to use when caching it. The first usage for this operation is to opcode-cache the PHP code managed by PCS, which is essential when considering migrating part of a core extension from C to PHP. Please note that the PR *does not* include the changes to make opcache use this new mechanism. The reason is that the required changes are far from trivial, the opcache code is complex, and I prefer someone more familiar with it to implement the changes. Please comment. Regards François