Sure using the QueryString is an easy way to pass
information from one ASP page to another, but there
is a limit to the amount of information you can
squeeze into the address bar.
For a lot of uses the QueryString is a better choice for
data transfer then the Form collection. It allows for
bookmarking of result pages, simple debugging, and
you don't have to use a form to utilize it, but there is
one place it falls short: the amount of data you can transfer.
The amount of data you can transfer on the QueryString
is limited by a number of factors, but the one that seems
to be the most restrictive is the space in your browser's
address bar. The Internet Explorer versions 5 and 6 that I
tested only allowed up to 2,047 characters while Netscape
Navigator version 4 seemed to be able to handle up to 30,000
and I couldn't get version 6 much past 9,000.
Before you start thinking that 2,047 is a lot, it's
not like you can go ahead and use all of those characters.
That limit is even less once you deduct the address of your
site, the path to the requested file, and even the requested
Even with those deductions, you're still left some space
to play with, but realize that it's not endless.
For those occasions when you can't determine how much data
you'll be moving around ahead of time or when you're using
a textarea element, it might make sense to use
a post to the Form collection just to be on the safe side.