From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stuart D. Herring" Newsgroups: gmane.emacs.devel Subject: Re: Patch for remote files in dnd.el Date: Thu, 7 Sep 2006 08:50:37 -0700 (PDT) Message-ID: <33097.128.165.123.18.1157644237.squirrel@webmail.lanl.gov> References: <44FFD45C.7010206@gnu.org> Reply-To: herring@lanl.gov NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1157644274 24470 80.91.229.2 (7 Sep 2006 15:51:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 7 Sep 2006 15:51:14 +0000 (UTC) Cc: Jan =?iso-8859-1?Q?Dj=E4rv?= , emacs-devel@gnu.org, Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 07 17:51:12 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GLM9f-0000pF-9B for ged-emacs-devel@m.gmane.org; Thu, 07 Sep 2006 17:51:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GLM9e-00029J-R2 for ged-emacs-devel@m.gmane.org; Thu, 07 Sep 2006 11:51:02 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GLM9Q-000293-Ef for emacs-devel@gnu.org; Thu, 07 Sep 2006 11:50:48 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GLM9P-00028j-91 for emacs-devel@gnu.org; Thu, 07 Sep 2006 11:50:48 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GLM9P-00028a-4Q for emacs-devel@gnu.org; Thu, 07 Sep 2006 11:50:47 -0400 Original-Received: from [192.65.95.54] (helo=mailwasher-b.lanl.gov) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GLM9l-0000KQ-29; Thu, 07 Sep 2006 11:51:09 -0400 Original-Received: from mailrelay1.lanl.gov (mailrelay1.lanl.gov [128.165.4.101]) by mailwasher-b.lanl.gov (8.13.6/8.13.6/(ccn-5)) with ESMTP id k87FocuH029429; Thu, 7 Sep 2006 09:50:39 -0600 Original-Received: from webmail1.lanl.gov (webmail1.lanl.gov [128.165.4.106]) by mailrelay1.lanl.gov (8.13.6/8.13.6/(ccn-5)) with ESMTP id k87Foc5w001983; Thu, 7 Sep 2006 09:50:38 -0600 Original-Received: from webmail1.lanl.gov (localhost.localdomain [127.0.0.1]) by webmail1.lanl.gov (8.12.11.20060308/8.12.11) with ESMTP id k87FocSb028702; Thu, 7 Sep 2006 09:50:38 -0600 Original-Received: (from apache@localhost) by webmail1.lanl.gov (8.12.11.20060308/8.12.11/Submit) id k87FobDS028700; Thu, 7 Sep 2006 08:50:37 -0700 X-Authentication-Warning: webmail1.lanl.gov: apache set sender to herring@lanl.gov using -f Original-Received: from 128.165.123.18 (SquirrelMail authenticated user 196434) by webmail.lanl.gov with HTTP; Thu, 7 Sep 2006 08:50:37 -0700 (PDT) In-Reply-To: Original-To: "YAMAMOTO Mitsuharu" User-Agent: SquirrelMail/1.4.6-7.el3.7lanl X-Priority: 3 (Normal) Importance: Normal X-PMX-Version: 4.7.1.128075 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:59514 Archived-At: > I'm not sure if file:////REMOTEHOST/DIRECTORY/NAME or > file://localhost//REMOTEHOST/DIRECTORY/NAME is invalid or not. But > even the current code uses invalid file:/DIRECTORY/FILE. :-) See RFC 3986, section 3.2.2. file:/dir/file is equivalent to file:///dir/file and to file://localhost/dir/file. In the first two cases you mention, the "path" component of the URI is "//REMOTEHOST/DIRECTORY/NAME", and it is up to the authority (in this case, the system file name interpreter and file system) to determine its meaning; presumably Windows interprets "//R/D/N" as being a UNC path. The trick is in section 3.3: URIs without authority components (like "file:/DIRECTORY/FILE") can't have paths that begin with two slashes, since two slashes begin the authority. So "file://REMOTEHOST/DIRECTORY/NAME" is a file on a machine whose FQDN is REMOTEHOST (according to RFC 1738), although I imagine that most systems would simply attempt to resolve REMOTEHOST as a hostname (thus succeeding with local names and local DNS systems) or, perhaps, would use some sort of file-sharing protocol (like SMB) and interpret REMOTEHOST as an identifier for use with it. In short, "file:/dir/file" is valid, but perhaps only one of "file://host/dir/file" and "file:////host/dir/file" will work (with any given file-sharing arrangement). Whichever mode seems to work with existing arrangements should be used (even for local files, for consistency). Are there even any schemes in common use other than UNC? NFS in typical use doesn't involve URIs, and even in "public handle" use involves nfs: URIs, not file:. URIs are confusing business! Hope this helps. Davis -- This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.