I'm faced with a dilemma. I'm trying to be a good RFC consumer and  
stick with the true purpose of GET and POST (see 
http://www.cs.tut.fi/~jkorpela/forms/methods.html 
  for a good discussion on the history of these two HTTP verbs).  
Plainly put, GET is for retrieving data and POST is for creating data.  
However, the problem lies in the fact that their purpose and their  
data encoding mechanism are mutually exclusive. GET requests encode  
data in the URL and POST requests encode data into the form. However,  
it is not always desirable to issue a GET request with URL-encoded  
data (login information for example), not is it always desirable to  
POST data with a form (sometimes a query string will do).

I'm curious what others think of the differences between GET and POST  
and whether it is still desirable to think of them as separate verbs  
or rather just two means to accomplish the same thing with different  
encoding techniques.

Thanks!

-- 
-a

"Only two things are infinite, the universe and human stupidity, and  
I'm not sure about the former."  --Einstein

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2394107

Reply via email to