Subj : Re: Software Job Market Myths
To   : comp.programming,comp.software-eng
From : T Beck
Date : Tue Aug 16 2005 02:30 pm


Chris Sonnack wrote:
> Steve O'Hara-Smith writes:
>
> >> That is, when it's *appropriate* to use GET or POST....
> >
> > What you mean like there's a limit on URL length but you can
> > POST as much as you like ?
>
> True, but nope, not the one.
[snip]


I believe what Chris is looking for is this:

Get -- you want to use Get when you have some page which is publicly
accessable and has certain variables set to get to a specific state.
ie: search page.  By putting everything in the GET line, it can be
bookmarked, copied to an e-mail (or IM or whatever) and shared with
friends/colleagues

Post -- you generally want to use POST when a password is involved, or
any information you do not want someone to be able to bypass the
initial portions of a page to get to.  This includes anything where
someone should login & be verified, or even simple stuff like a public
anonymous voting page.

The key differences to note are that a GET is way more public in a
sense..

(don't think I'm advising people just send passwords through POST for
most applications, but sometimes, depending on your requirements, it
can be allowable to send as a hash via POST, IMHO)

--T Beck

.