Bob Ippolito wrote:
On Dec 6, 2005, at 6:20 PM, Peter Hansen wrote:
Bob Ippolito wrote:
http://en.wikipedia.org/wiki/
XMLHttpRequest#Microsoft_Internet_Explorer_Cache_issues
From the sounds of that, using POST instead of GET would avoid the
issue. It appears MochiKit.Async uses GET to do its work. What
would be the downside of using POST instead?
That sounds absolutely terrible.
At least adding some random stuff to the URL doesn't change the
semantics, but it's not typically that hard to add a header or two on
the server side to remove the need for that.
As someone who is using AJAX to access only his own servers (i.e. I'm in
control of both sides) I don't fully understand why it would be
absolutely terrible. From my point of view, POST vs. GET is a total
wash. My server code generally doesn't know which was used (for forms,
anyway... am I off-base in the world of AJAX services?).
I assume there are services where you *must* access it using only GET.
And, since MochiKit doesn't use POST even as an option, I also assume
there are no useful AJAX services which require a POST. And since there
are limits on the size of GET URLs in many places (as I recall) I
further assume nobody is concerned about being force to use GET.
As a non-expert in this whole area, I'd be happy to have my assumptions
all shot down... :-)
-Peter
