The enormity of the consequences of HTML only allowing GET and POST cannot be overstated IMO. It's maybe the most damaging technical decision in the web standards space - ever. I see HTML forms as a root cause for the WS-* "everything goes over POST" debacle, a billion dollar industry mistake, at best.
I've always wondered what's the history behing the GET/POST only restriction in HTML. Was there a good reason (or did something appear to be good reason) for doing so? I can't think of one.
O how enjoyably retarded.
How about using a RESTful explanation for things to explain why. Or maybe another useful buzzword, “YAGNI”, I dunno, doesn’t matter, cuz, gee wow, looks like whoever whenever made the right choices for the web to be the screaming success that it is.
Seriously, what you’re doing here is postmortem on the web. The web, people. The web. You’re saying something was wrong when the web was implemented in browses, and now all we’ve got to show for it is….the web.
Wow.
said:
Not entirely sure what you intend to say (except for insulting me on my own blog). I didn’t even say something was wrong, I just wondered why the HTTP and HTML standards don’t match.
Luckily, Matt’s comment provides an answer.
for me it looks pretty obvious. Could you imagine the mess it would be if people could mess with PUT and DELETE at will?
JJ-
said:
@JJ: Why would the mess be any worse than when using POST?
HTTP 1.0 defined only GET, POST, and HEAD. By the time HTTP 1.1 standardized other methods, HTML was probably too bogged down in the browser wars to adapt.