Re: HTML+ and automated forms

• Mail folder: WWW Talk Apr 94-present
• Next message: Christian L. Mogensen: "Re: HTML+ and automated forms"
• Previous message: burchard@geom.umn.edu: "Which browser generates these errors?"
• Maybe in reply to: Alastair Aitken CLMS: "HTML+ and automated forms"
• Reply: Christian L. Mogensen: "Re: HTML+ and automated forms"

Errors-To: listmaster@www0.cern.ch
Date: Mon, 27 Jun 1994 22:16:54 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <94Jun27.131346pdt.2760@golden.parc.xerox.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: masinter@parc.xerox.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Larry Masinter <masinter@parc.xerox.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: HTML+ and automated forms
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

We're looking for a way that a form can ask for the user to supply a
'file', with full MIME typing associated with that file, e.g., the
form element would want to specify 'Accept:' headers. 

For example, if this were a fax service, it could Accept: text/*,
application/postscript, image/* (but not, say, audio/*); if it were a
answering-machine application, it might accept only audio/*.

The client would do the appropriate thing for the client application,
e.g., prompt for a file name of the appropriate type, or, if audio was
being accepted, allow for recording of an audio clip...

The question is, what's the `right way' to handle this between HTML
and HTTP? Does this require a separate protocol? Should the `Accept:'
headers be part of the form?

Personally, I like putting them in the form if only so that you could
mail someone a form rather than always deliver it to them via http...