Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15872
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 99040 invoked by uid 1010); 6 Apr 2005 15:02:32 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 99025 invoked from network); 6 Apr 2005 15:02:32 -0000
Received: from unknown (HELO osu1.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Apr 2005 15:02:32 -0000
X-Host-Fingerprint: 69.12.155.130 69-12-155-130.dsl.static.sonic.net Linux 2.4/2.6
Received: from ([69.12.155.130:3552] helo=pigeon.alphaweb.net)
	by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP
	id B8/D4-19272-70AF3524 for <internals@lists.php.net>; Wed, 06 Apr 2005 11:02:31 -0400
Received: from localhost ([127.0.0.1] helo=lighthammer)
	by pigeon.alphaweb.net with smtp (Exim 4.10)
	id 1DJBf1-0002af-00; Wed, 06 Apr 2005 07:37:39 -0700
Message-ID: <003801c53ab9$a7902650$6c051fac@lighthammer>
To: "Wez Furlong" <kingwez@gmail.com>,
	"Morgan L. Owens" <packrat@nznet.gen.nz>
Cc: <internals@lists.php.net>
References: <425369FD.1000800@nznet.gen.nz> <4e89b4260504060541544ccde2@mail.gmail.com>
Date: Wed, 6 Apr 2005 08:02:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Subject: Re: [PHP-DEV] Scheme identification in stream wrappers
From: pollita@php.net ("Sara Golemon")

> You know, I could have sworn that I only looked for a : as the separator.
>
Not according to php_stream_locate_url_wrapper():

    for (p = path; isalnum((int)*p) || *p == '+' || *p == '-' || *p == '.'; 
p++) n++;

    if ((*p == ':') && (n > 1) && !strncmp("://", p, 3)) {
        protocol = path;
    } else if (strncasecmp(path, "zlib:", 5) == 0) {
        ...
    }

Which of course says: "It it ain't [a-zA-Z0-9+.-]+://, and it ain't zlib:, 
then it ain't a wrapper."

> I seem to remember a discussion about this in the past, but don't
> recall the details.
>
The only thing that positively leaps to mind is the ability to 
read-from/write-to alternate data streams under win32.   But I suppose that 
could be worked around easily enough.  If nothing else an explicit file:// 
scheme when that's needed would remedy the problem.  Remind me what the 
*nixes do with ':' ?

-Sara