Aengus Lawlor wrote:
> Well, it's standard in the sense that the only mechanism for choosing
> multiple parameters in HTML is the <SELECT MULTIPLE> tag, which works by
> sending <key>=<value> with the same key repeated multiple times. There's
> nothing to say that an application _must_ handle multiple instances of a
> single key, because there's nothing to say that an application _must_
> handle every single key=value pair.
>
Also, if multiple check boxes are given the same name you'll get multiple key=value
pairs for the same keyname. Although why anyone would want to do this....
I had thought there was another instance of forms generating multiple key=value
pairs for a single keyname, but I can't think of any that wouldn't be contrived like
my example.
Then again, all the browsers build CGI strings by separateing the variables with an
'&' and the "HTML people" (RFC 1833, I think) stand by their recommendation that
this should be something different like ';'. So I guess I shouldn't say there's any
"standard" in CGI calls.
However, the Perl and ASP CGI libraries (and I think Netscapes Server-Side
JavsScript library too) understand the kind of response you get from a <SELECT
MULTIPLE> and offer nice ways of getting that data (e.g. hash/collection).
So, yeah, it's not broken, but it wouldn't be hard to implement both.
--
Jeremy Wadsack
OutQuest Magazine
a Wadsack-Allen publication
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
