Re: Idea for new form input type

Dave_Raggett <dsr@hplb.hpl.hp.com>
Errors-To: listmaster@www0.cern.ch
Date: Fri, 25 Feb 1994 15:53:42 --100
Message-id: <9402251107.AA04912@manuel.hpl.hp.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: dsr@hplb.hpl.hp.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Dave_Raggett <dsr@hplb.hpl.hp.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Idea for new form input type
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 885
> This approach would not address the problem of non text files very well.
> Should a CGI script have to be prepared to handle a MS Word document as
> well as ASCII text from a text area field?

> Should the form allow the specification of a desired/required MIME content
> type for the file to be named?

> Should there be a mechanism for specifying the MIME content type of the
> file to be sent?

Yes this is essential and provides the means for encapsulating form contents
as a multipart MIME message. CGI scripts will be able to then process the
data accordingly. MIME messages can have nested parts, so the TEXTAREA field
would map to a nested multipart message when multiple objects have been
"dropped" into that field.

This idea and the Lou's simpler file name field needs to be discussed at the
WWW Conference in May along with other ideas for extending forms.

Dave Raggett