Re: Auto-Download tags/function?
Martijn Koster <m.koster@nexor.co.uk>
Errors-To: listmaster@www0.cern.ch
Date: Thu, 19 May 1994 10:40:36 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9405190834.AA25001@dxmint.cern.ch>
Errors-To: listmaster@www0.cern.ch
Reply-To: m.koster@nexor.co.uk
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Martijn Koster <m.koster@nexor.co.uk>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Auto-Download tags/function?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Dan wrote:
> A looooooong time ago, I suggested:
>
> <A HREF="ftp://host/file.tar.Z" CONTENT-TYPE="application/x-tarZ">
> a tar file</a>
I don't think this should be in the link either, it rules out protocol
specific type negotiation.
> which would be enough information for the browser to decide that
> the tar file is not something it can display in the reading window.
>
> The concept was introduced in the MIME RFC. I thought we should
> use it. I got vetoed, cuz timbl (and others) thought such things belong in
> the protol. But this rules out FTP as a protocol. But wait! we
> do use FTP protocol. So we end up with the current broken situation.
Different systems (protocols) need different methods to determine this
sort of thing. I don't see why a broswser couldn't use filenames
extensions as a type indication when using FTP only. After all that
is how a manual FTP session works.
-- Martijn
__________
Internet: m.koster@nexor.co.uk
X-400: C=GB; A= ; P=Nexor; O=Nexor; S=koster; I=M
X-500: c=GB@o=NEXOR Ltd@cn=Martijn Koster
WWW: http://web.nexor.co.uk/mak/mak.html