POST vs GET, an existantial question

[dreeze]

From what I understant, the difference is only in the way the parameters are attached to the request.
one is appended to the URL, the other is sending it after a newline character.
my question is why do servers treat them so seperataly if it is a small difference. I really dont see the difference that would justify implementing a whole seperate function and/or class depending on a POST or GET.
I searched the web, and each of my findings only had that as a justification,
can someone shed some light on this?

 

[strantheman]

So are you attempting to discount the use of URL parameters altogether? Or are you simply trying to understand how server's interpret them, and why they would interpret each seperately?

I use URL parameters sparingly, but there are times when its absolutely necessary.

 

[tsdragon]

According to the HTML/CGI spec (I can't remember exactly where I read it), GETs are only supposed to be used where the values passed will not change (for example, in links which pass a parameter to a progam), and browsers are supposed to feel free to cache GET requests. PUTs are supposed to be used for forms where the values may change repeated over the course of a browser session, and browser should NOT cache PUT requests. Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard.

 

[dreeze]

strantheman,
im not trying to discount anything, i simply wanted to understand the fundamental difference between the two as you say.

thanks guys for the posts, the caching story would make some sense and justify using one over the other to assure higher security.