Author orsenthil
Recipients ajaksu2, brian.curtin, denversc, dstanek, eric.araujo, ezio.melotti, ipatrol, jackdied, jjlee, jorend, koder_ua, orsenthil, pitrou, poke, santoso.wijaya
Date 2011-10-11.10:02:07
SpamBayes Score 1.17614e-06
Marked as misclassified No
Message-id <1318327328.9.0.464501410897.issue1673007@psf.upfronthosting.co.za>
In-reply-to
Content
Patrick, 

Lots of valid points. I had not looked at the RFC spec when I mentioned about data over request (GET) method, but was trying to derive the current functionality of module (so that users can have a seamless experience) with additional method="GET" as default.  Note, my intention was to be explicit when we give method arg.

But yeah, when user has specified the methods (PUT/DELETE etc) and given the data, correct rules should apply on how that method should deal with data.

As you pointed out to RFC, I realize RFC clearly points out the data (message-body) should be ignored and method should be given preference, whenever specification of method has nothing to with data.  I should take back my argument on giving data as preference even over GET.

Now, question arises- Can we in anyway default the method="GET" and maintain compatibility as well consistency with user expectations? At the moment, just by sending data over Request, the method is assumed to be POST. If that is not possible, then the way, current patch does seems to be a good way to acheive the purpose.
History
Date User Action Args
2011-10-11 10:02:09orsenthilsetrecipients: + orsenthil, jjlee, jorend, pitrou, dstanek, jackdied, ajaksu2, koder_ua, ezio.melotti, eric.araujo, brian.curtin, poke, ipatrol, santoso.wijaya, denversc
2011-10-11 10:02:08orsenthilsetmessageid: <1318327328.9.0.464501410897.issue1673007@psf.upfronthosting.co.za>
2011-10-11 10:02:08orsenthillinkissue1673007 messages
2011-10-11 10:02:07orsenthilcreate