Re: support of default document names

• Mail folder: WWW Talk Jan 94-present
• Next message: Kevin Altis: "Re: Mosaic update?"
• Previous message: Bob Kaehms: "WAIS -> WWW Gateway and Titles (fwd)"
• Maybe in reply to: George Phillips: "support of default document names"

Errors-To: listmaster@www0.cern.ch
Date: Sat, 26 Feb 1994 01:40:59 --100
Message-id: <m0paD22-00041aC@ibeam.intel.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: altis@ibeam.jf.intel.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: altis@ibeam.jf.intel.com (Kevin Altis)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: support of default document names
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 1226

At  3:39 PM 2/25/94 -0800, George Phillips wrote:
It is sad about Motif and the save as dialog, but then that's Motif. Other
window managers, plus Windows, Mac, and the numerous other browsers
appearing don't have that problem with saving. One would hope we don't ever
cripple part of the Web architecture just because you can't implement a
feature cleanly under Unix, Motif, etc. :)

>Alternately, one could add a "Document-Name: " header.  Same difference,
>but maybe an extra header is more MIMEish.

Since the name="" is already used with MIME Content-type: headers, there's
no sense in inventing a new metainformation field. Also, I don't think the
extra metainformation field would work with a multipart MIME message, but I
do know that Content-type: is always going to be there for each piece of a
multipart MIME message, so the name="" method works regardless.

I would also expect that if you were to mail an HTML document to me from
your browser, the browser would put name="" info. on the Content-type:
header so my mail program would have a clue. When your browser mailed a
multipart MIME message with an TEXT, HTML, and PostScript version of the
document, each Content-type: would be labeled appropriately.

ka