- From: <bugzilla@jessica.w3.org>
- Date: Sat, 09 Apr 2011 02:10:51 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10671 Paolo Perrotta <paolo.nusco.perrotta@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paolo.nusco.perrotta@gmail. | |com --- Comment #12 from Paolo Perrotta <paolo.nusco.perrotta@gmail.com> 2011-04-09 02:10:48 UTC --- > To paraphrase the fundamental requirement for supporting these methods on > forms: > so that a real human is able to interact natively with a Restful system using > plain html, no ajax or other workarounds. Speaking as a developer, I think this is reason enough to have PUT/DELETE in forms. This feature would be useful in documenting, debugging, prototyping, manual testing and automated testing. The ramifications for the domain of web services could range quite far. Self-documentation in particular is perceived as a weak spot of REST services when compared with SOAP services. I also see another advantage of PUT/DELETE in forms: they let the browser know that you're doing something idempotent. When you issue a POST through a form and then hit the "back" button (or you hit "refresh" before the response has come through), the browser has no choice but to show you a scary confirmation dialog, that regularly perplexes non-technical users. With PUT/DELETE, browsers could choose to just re-submit, or at least show you a dialog that's more informative. Ajax wouldn't help there, because it happens behind the browser's back. Just my 2 cents. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 9 April 2011 02:10:53 UTC