Re: file://host/location URLs

[Daniel Colascione <dancol@dancol.org>]

[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]

On 11/20/2012 4:54 AM, Jason Rumney wrote:
> Daniel Colascione <dancol@dancol.org> writes:
> 
>> Yes, my proposal violates the RFC. I maintain that nobody deliberately
>> constructs file URLs pointing to remote hosts
> 
> I do it all the time.  Windows has a well defined default protocol for
> accessing remote files on named hosts, and such URLs mostly work (they
> even used to work on Emacs IIRC until url-handler came along and started
> forcing them over to FTP).

Yes, the Windows remote access mechanism is good, party because applications
don't need to be aware of it to use it. They can just use normal filesystem
access APIs. If we treat file URIs as simple filenames, remote access under
Windows will continue to work.

> GNOME, KDE and others may also have mechanisms for dealing with remote
> file URLs that we could use.

All right, let me make a different proposal: by default, we'll treat file://
URIs with non-localhost host parts as errors, since FTP is seldom appropriate.
On Windows and Cygwin systems, we'll treat file://foo/bar/qux as
file:///foo/bar/qux since the underlying OS understands how to access host foo.
If someone wants to integrate Emacs with gnome-vfs, he can update the file-URI
code at that time.

File URI handling seems to be generally broken for local files anyway. Try
(find-file "file://localhost/etc/passwd").


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]