It's quite common (and useful) to have multiple values associated with one name. These aren't keys in the same sense that unique identifiers are in a database. Considering the following:

You're creating a Web page where people can sign up for mailing lists on their favorite sports. You have the following HTML:

<input type="checkbox" name="football" value="football">
<input type="checkbox" name="soccer" value="soccer">
<input type="checkbox" name="tiddly winks" value="tiddly winks">
[download]

In your code, you check for each of those values and subscribe the person to the mailing list appropriately. However, as time goes on, your site becomes wildly popular and you are looking at your IPO. You include more and more sports, but your scripts are becoming difficult to maintain because you have to test for each and every sport individually. Instead, change your HTML to the following:

<input type="checkbox" name="sports" value="football">
<input type="checkbox" name="sports" value="soccer">
<input type="checkbox" name="sports" value="tiddly winks">
[download]

Your query string will resemble the following (if they check both football and tiddly winks):

sports=football&sports=tiddly%20winks
[download]

In your script, you'd have something like the following:

my @sports = $q->param('sports');
foreach my $sport ( @sports ) {
    # subscribe them to the list
}
[download]

That is much simpler than having separate names for each sports. Programmatically, it's the way to go.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.