Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51611 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42568 invoked from network); 7 Mar 2011 21:49:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2011 21:49:47 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:40907] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3F/F0-36910-7D2557D4 for ; Mon, 07 Mar 2011 16:49:12 -0500 Received: by vws10 with SMTP id 10so4178072vws.29 for ; Mon, 07 Mar 2011 13:49:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UWKX1ujq4t1ZmC9IhtCJuDYSRfgDrekKXfAdk7UbnoU=; b=bMrqx/6KoAyhEnVtSbP6OCwzgKXrO14wjvuw612FY7tZTvNEFIbgs9Mau+sGqxadT1 QKynVOcnTFBU1DImN7r/b8uJBJ1ULY16mGRb3PkW4bZu7HlcxdEO27Ewweg+STXpL/hZ lODduJItV/hjPbsoASiQIx/8ZLlo/Ci424RK8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=CpFjap/vLp3IUeIBidq1lXPlw+i4XcKJlVfHYY9UwnViGxntuJMIMA9+Pl7hDt4qWO dn0/NY8Ga5JypHecNKSl5vpNFcWrWNwh1IaI4bwZ1j8YahzcV0JwNgmFVOOTnXg/QAlN kItTBac8j1L9cU0JxGecad88eGLGfNsJYsGjw= MIME-Version: 1.0 Received: by 10.52.68.168 with SMTP id x8mr3789070vdt.158.1299534548710; Mon, 07 Mar 2011 13:49:08 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.52.164.165 with HTTP; Mon, 7 Mar 2011 13:49:08 -0800 (PST) In-Reply-To: <4D754EED.5080909@sugarcrm.com> 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> Date: Mon, 7 Mar 2011 22:49:08 +0100 X-Google-Sender-Auth: 01pszoJkQ1GM6V9MS_uRH1j6kck Message-ID: To: Stas Malyshev Cc: Pierre Joye , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=20cf307f3bb826337d049deb7709 Subject: Re: [PHP-DEV] file streams & metadata From: info@tyrael.hu (Ferenc Kovacs) --20cf307f3bb826337d049deb7709 Content-Type: text/plain; charset=UTF-8 On Mon, Mar 7, 2011 at 10:32 PM, Stas Malyshev wrote: > Hi! > > > That was also the reasons why they are not present in our stream >> implementation. I could image something for touch (there is a FR for >> it afair) as it is very easy to emulate on stream where it could not >> work, but really not for ch*. >> > > We have chmod now defined on all systems. However good or bad it is, I see > no problems in doing the same for streams. Streams that don't have this > semantics are free to not define this handler or not to support this > particular option, as happens with other optional handlers - e.g., mkdir > makes no sense for sockets, but that doesn't prevent mkdir from existing in > streams or socket streams from working fine. If you look at the docs, you > see there's even a section for streams saying what's supported and what's > not by particular stream, so obviously streams not supporting some > capabilities always were fine. So where's the problem? > > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > 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 --20cf307f3bb826337d049deb7709--