Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13575
Return-Path: <rrichards@ctindustries.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 96902 invoked by uid 1010); 27 Oct 2004 18:24:49 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 96873 invoked from network); 27 Oct 2004 18:24:49 -0000
Received: from unknown (HELO ctindustries.net) (216.117.147.250)
  by pb1.pair.com with SMTP; 27 Oct 2004 18:24:49 -0000
Received: from ctdprimary (dsta-aa203.pivot.net [66.186.171.203])
	(authenticated bits=0)
	by ctindustries.net (8.12.8/8.12.8) with ESMTP id i9RHKos3019173;
	Wed, 27 Oct 2004 13:20:52 -0400
Message-ID: <069e01c4bc52$bc930b70$f7dea8c0@cyberware.local>
To: "Moriyoshi Koizumi" <moriyoshi@at.wakwak.com>
Cc: <internals@lists.php.net>
References: <064a01c4bb82$8f9d4d90$f7dea8c0@cyberware.local> <417E929B.2040301@cschneid.com> <078e01c4bb96$86a0f340$f7dea8c0@cyberware.local> <4e89b4260410261323dc4d6da@mail.gmail.com> <044201c4bc31$38b32360$f7dea8c0@cyberware.local> <D0DCEECC-283C-11D9-A3BC-000A95CE0C62@at.wakwak.com>
Date: Wed, 27 Oct 2004 14:28:19 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Subject: Re: [PHP-DEV] Re: streams file uri under windows
From: rrichards@ctindustries.net ("Rob Richards")

From: Moriyoshi Koizumi

> Couldn't file://127.0.0.1/... or file://[::1]/... be valid URL's
> for the local resources?

 To play it safe I would say no right now. The file uri stuff is being
worked on again:
http://www.ietf.org/internet-drafts/draft-hoffman-file-uri-01.txt

It looks like it is safe to use the following (just implementing empty host
and "localhost" in the streams case for now) as a guideline as other
possible host definitions are being discussed but they all at least include
the following:
   where <host> is the fully qualified domain name of the system on
   which the <path> is accessible, and <path> is a hierarchical
   directory path of the form <directory>/<directory>/.../<name>.

   As a special case, <host> can be the string "localhost" or the empty
   string; this is interpreted as "the machine from which the URL is
   being interpreted".Rob