Re: FORM ENCTYPE=multipart/www-form (was: Toward closure on HTML)
weber@eit.COM (Jay C. Weber)
Errors-To: listmaster@www0.cern.ch
Date: Wed, 6 Apr 1994 19:27:23 --100
Message-id: <9404061724.AA02703@eit.COM>
Errors-To: listmaster@www0.cern.ch
Reply-To: weber@eit.COM
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: weber@eit.COM (Jay C. Weber)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: FORM ENCTYPE=multipart/www-form (was: Toward closure on HTML)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 829
> From: wmperry@indiana.edu (William M. Perry)
>
> But who decides when something should be moved from the
> application/www-form-url-encoded block to a block of its own? Simply
> saying 'only textarea, scribble, audio, and image/*' might not be 100%
> accurate. What happens when there is a very long 'text' block? It is
> conceivable if someone doesn't put a MAXLENGTH into an <input type=text>
> that someone could type in 10000 characters (I believe that was the default
> Maxlength attribute).
That choice can be made entirely by the client, which could get arbitrarily
sophisticated, but I suspect it will end up being a matter of programming
convenience. In that case, I think all <input type=text> fields will end
up in catch-all blocks. Won't matter much to servers, it's just a minor
change of overhead.
Jay