Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90979 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51417 invoked from network); 27 Jan 2016 12:45:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jan 2016 12:45:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:23842] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/F8-28185-5EBB8A65 for ; Wed, 27 Jan 2016 07:45:25 -0500 Received: from [127.0.0.1] (unknown [82.240.16.115]) (Authenticated sender: flaupretre@free.fr) by smtp2-g21.free.fr (Postfix) with ESMTPSA id 292B34B0190; Wed, 27 Jan 2016 13:43:24 +0100 (CET) To: internals@lists.php.net, Julien Pauli References: <9D.00.64206.7C430A65@pb1.pair.com> <0D.E3.12955.15522A65@pb1.pair.com> Message-ID: <56A8BBDC.3090408@php.net> Date: Wed, 27 Jan 2016 13:45:16 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 160127-0, 27/01/2016), Outbound message X-Antivirus-Status: Clean Subject: Re: [PHP-DEV] Severe safety fail in file access and stream filters From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Le 26/01/2016 11:50, Julien Pauli a écrit : > > I think what we should do is sit around the table with people > interested (Daniel Lowrey may be one of them), and plan a full rewrite > of streams for PHP next major (PHP 8). I don't think addind stuff to > next minors is a good idea, knowing we must prevent BC breaks in such > versions. We'll probably have to introduce some BC breaks is our tidy. > > All our stream API is missing lots of features, and failing in many parts. > > We could as well add to the reflection Async I/O and scatter/gather, +1 for a major rewrite in version 8. Examining every streams-related feature requests would be a good start, IMO. I also have several improvements in mind. So, I'd be glad to be included in the process. Regards François