Re: request for new forms submission consensus

• Mail folder: WWW Talk Oct 93-present
• Next message: Kevin Altis: "Re: request for new forms submission consensus"
• Previous message: Pei Y. Wei: "Re: request for new forms submission consensus"
• Maybe in reply to: Tony Sanders: "Re: request for new forms submission consensus "
• Reply: Tony Sanders: "Re: request for new forms submission consensus "

X-Delivered: at request of secret on dxcern.cern.ch
Errors-To: sanders@bsdi.com
Message-id: <9310111827.AA27717@austin.BSDI.COM>
To: www-talk@nxoc01.cern.ch
Subject: Re: request for new forms submission consensus 
In-Reply-To: Pei Y. Wei's message of Mon, 11 Oct 93 10:48:57 PDT.
Errors-To: sanders@bsdi.com
Reply-To: sanders@bsdi.com
Organization: Berkeley Software Design, Inc.
Date: Mon, 11 Oct 1993 13:27:49 -0500
From: Tony Sanders <sanders@bsdi.com>

[on forms submission]
> too long from now one of those forms will be "type=audio" :), and when
Very good point.  I second the vote to use MIME encodings.  However, this
doesn't preclude using the encoding we have now under POST with a simple
MIME header.  Then we can easily move to more complex forms like
multipart/mixed (example below).

A simple form example:
    POST /hyplan/sanders.html HTTP/1.0
    MIME-Version: 1.0
    Content-type: application/x-www-textform

    name=test&address=data

A complex example (with an audio part):
    POST /hyplan/sanders.html HTTP/1.0
    MIME-Version: 1.0
    Content-type: multipart/mixed; boundary="unique string"

    --unique string
    Content-Type: application/x-www-textform

    name=test&address=data
    --unique string
    Content-Type: audio/basic
    Content-Transfer-Encoding: BASE64

    SDFLKjfllkjLKJhJHhjGjHGjHSJfhLSKDJFHjsdhfkJSDHFKSJH
    --unique string--

--sanders