Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13576 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85462 invoked by uid 1010); 27 Oct 2004 18:45:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 85307 invoked from network); 27 Oct 2004 18:45:38 -0000 Received: from unknown (HELO mgkyb2.nw.wakwak.com) (211.9.231.193) by pb1.pair.com with SMTP; 27 Oct 2004 18:45:38 -0000 Received: from vckyb3.nw.wakwak.com (postfix@vckyb3.nw.wakwak.com [211.9.231.144]) by mgkyb2.nw.wakwak.com (8.13.1/8.13.1/2004-08-10) with SMTP id i9RIjaOO034238; Thu, 28 Oct 2004 03:45:36 +0900 (JST) (envelope-from moriyoshi@at.wakwak.com) Received: from at.wakwak.com (at.wakwak.com [211.9.230.135]) by vckyb3.nw.wakwak.com (Postfix) with ESMTP id F14123FE03; Thu, 28 Oct 2004 03:45:35 +0900 (JST) Received: from [192.168.0.100] (newcycle.as.wakwak.ne.jp [218.225.209.145]) (pbs=a6jjyb) by at.wakwak.com (8.13.1/8.13.1/2004-09-09) with ESMTP/inet id i9RIjZG4003234; Thu, 28 Oct 2004 03:45:35 +0900 (JST) (envelope-from moriyoshi@at.wakwak.com) In-Reply-To: <069e01c4bc52$bc930b70$f7dea8c0@cyberware.local> References: <064a01c4bb82$8f9d4d90$f7dea8c0@cyberware.local> <417E929B.2040301@cschneid.com> <078e01c4bb96$86a0f340$f7dea8c0@cyberware.local> <4e89b4260410261323dc4d6da@mail.gmail.com> <044201c4bc31$38b32360$f7dea8c0@cyberware.local> <069e01c4bc52$bc930b70$f7dea8c0@cyberware.local> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <4ADB33A2-2848-11D9-A3BC-000A95CE0C62@at.wakwak.com> Content-Transfer-Encoding: 7bit Cc: Date: Thu, 28 Oct 2004 03:44:54 +0900 To: "Rob Richards" X-Mailer: Apple Mail (2.619) Subject: Re: [PHP-DEV] Re: streams file uri under windows From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi) On 2004/10/28, at 3:28, Rob Richards wrote: > 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 is the fully qualified domain name of the system on > which the is accessible, and is a hierarchical > directory path of the form //.../. > > As a special case, can be the string "localhost" or the empty > string; this is interpreted as "the machine from which the URL is > being interpreted".Rob Convinced enough. I've never been told that "localhost" is such a magic spell :) Thanks for the clarification. Moriyoshi