Re: mosaic pre6 coming soon, and more forms stuff

Tony Sanders <sanders@bsdi.com>

Mail folder: WWW Talk Oct 93-present
Next message: Tim Berners-Lee: "HTTP mods: Variants, Derived-From:"
Previous message: Marc Andreessen: "mosaic pre6 coming soon, and more forms stuff"

X-Delivered: at request of secret on dxcern.cern.ch
Errors-To: sanders@bsdi.com
Message-id: <9310120406.AA03604@austin.BSDI.COM>
To: www-talk@nxoc01.cern.ch
Subject: Re: mosaic pre6 coming soon, and more forms stuff 
In-Reply-To: Your message of Mon, 11 Oct 93 22:21:47 PDT.
Errors-To: sanders@bsdi.com
Reply-To: sanders@bsdi.com
Organization: Berkeley Software Design, Inc.
Date: Mon, 11 Oct 1993 23:06:31 -0500
From: Tony Sanders <sanders@bsdi.com>

> fields for fill-out forms forms.  I have promised him that no one
> would use multiline text fields until we have a real submission method
> (which we now have, I think, from the recent discussion).  But we
One issue is what to call the content...  I vote we use:
    application/x-www-form-simple	for the current encoding style
    multipart/mixed			for complex forms (e.g., audio)

If we put the string in the message body (application/x-www-form-simple)
and treat it as binary it shouldn't matter how long the line is like it
does for the URL part.  MIME will take care of the rest (e.g., if it
needs to go through a mail gateway it could get encoded as BASE64).
BTW: I vote we start explicitly using:
    Content-Transfer-Encoding: BINARY
In the HTTP/1.0 protocol.  This will make it easier on mail based
transports to do the right thing.

multipart/mixed we can worry about later.

--sanders