Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51617 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40511 invoked from network); 8 Mar 2011 15:46:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Mar 2011 15:46:16 -0000 X-Host-Fingerprint: 208.107.178.23 host-23-178-107-208.midco.net Date: Tue, 08 Mar 2011 10:46:15 -0500 Received: from [208.107.178.23] ([208.107.178.23:18513] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5F/53-19125-74F467D4 for ; Tue, 08 Mar 2011 10:46:15 -0500 Message-ID: <5F.53.19125.74F467D4@pb1.pair.com> To: internals@lists.php.net References: <4D7431C3.10405@sugarcrm.com> <4D74A8FD.3020102@sugarcrm.com> <4D74AB3C.8040702@sugarcrm.com> <4D751AC2.3030800@sugarcrm.com> <4D7535E2.5040007@sugarcrm.com> <4D754997.5080704@sugarcrm.com> <4D754B73.1040800@sugarcrm.com> <4D754EED.5080909@sugarcrm.com> User-Agent: slrn/pre1.0.0-18 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit X-Posted-By: 208.107.178.23 Subject: Re: [PHP-DEV] file streams & metadata From: weierophinney@php.net (Matthew Weier O'Phinney) On 2011-03-08, Pierre Joye wrote: > On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs wrote: > > > From the sideline: > > it's hard to belive that there are no one else with opinion on this matter. > > I don't want to take sides because I don't have the necessary knowledge > > about the matter, but maybe it would be a good idea to write an RFC, and and > > maybe a POC, so we can see how intrusive would be the implementation. > > and if there are more bystanders, then please make your voice heard. > > Tyrael > > It is very easy to implement what Stas is asking. But that's not the > question. The question is should we do it? And my point is that we > should not do it like that, bad design, incomplete and limited > support. As a developer, in many cases I'd prefer something incomplete and limited in support to nothing at all. I've been bitten by the same issue Stas describes, and having a way to tie into touch and chmod in my stream wrappers would be incredibly useful -- even if it won't work with _every_ stream. -- Matthew Weier O'Phinney Project Lead | matthew@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc