Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36509 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31078 invoked from network); 25 Mar 2008 16:58:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Mar 2008 16:58:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 38.99.98.18 beast.bluga.net Linux 2.6 Received: from [38.99.98.18] ([38.99.98.18:56837] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/90-28012-A4F29E74 for ; Tue, 25 Mar 2008 11:58:51 -0500 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 13BB0C0F509; Tue, 25 Mar 2008 09:50:06 -0700 (MST) Received: from [129.93.124.129] (pcp041190pcs.unl.edu [129.93.124.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 89B58C0F4F6; Tue, 25 Mar 2008 09:50:04 -0700 (MST) Message-ID: <47E92D3B.7010500@chiaraquartet.net> Date: Tue, 25 Mar 2008 11:50:03 -0500 User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Dmitry Stogov CC: Stefan Walk , internals@lists.php.net, Stanislav Malyshev , Marcus Boerger References: <47E2F8FA.20107@chiaraquartet.net> <47E7FEFD.8080504@chiaraquartet.net> <47E800F1.5090101@zend.com> <200803251613.20245.et@php.net> <47E91898.5050503@zend.com> In-Reply-To: <47E91898.5050503@zend.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] REMINDER - stream wrappers in include_path From: greg@chiaraquartet.net (Greg Beaver) Dmitry Stogov wrote: > :( > Any ideas how to support this? > > Dmitry. > > Stefan Walk wrote: >> On Monday 24 March 2008 20:28:49 Stanislav Malyshev wrote: >>>> Beats me, I'm sure posix-based systems don't, but it is called "Uniform >>>> Naming Convention" so it's possible somebody might implement it >>> The fact that it's called "uniform" doesn't mean it works in anything >>> but Windows :) In UNIX IIRC if one needs to access SMB volume the >>> regular smb:// URLs are used, or tool-specific syntax. If you have >>> something like automount, then you have regular /-based URLs, but never >>> headr of // having any special meaning different from just /. >> >> a) // is valid for windows too >> b) cygwin uses // >> >> Regards, >> Stefan It is supported, have you tried it? Basically, the only way you could subvert this is if you have a relative path in your include_path, which would never work anyways, as include_path would change for every single file executed. To be clear, if there are any slashes in the path, the // will *not* be detected as a stream wrapper. Here is an example: oops.broken://UNC/path The code will detect this as a stream wrapper "oops.broken", but this example: /working.example://UNC/path will correctly detect "/working.example" and "//UNC/path" as 2 separate paths. Greg