Re: Separating GET and POST parameters

Jonathan Swartz <[email protected]> wrote:
> Taking different actions depending on whether a parameter was passed
> by GET or POST seems like a bad idea from the standpoint of code
> readability and coherence...and it will make your application non-
> portable, since most application frameworks will just merge the
> arguments. I'd recommend not going down this path.
>
> Jon

No way.  I think there's some reasonable arguments for seperating them out;
they are designed for different purposes.

Examples:
I might want to prevent someone from submitting their password via GET (less
secure).
I might want to prevent someone from submitting binary data via GET (very
likely to be invalid).
I might want to prevent someone from submitting a repeatable query (say, to
a search engine) via POST (not bookmarkable).

Best regards,
Jeremy Morton (Jez)



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click