Prototype doesn't actually use those methods--it uses POST (if not POST or GET), and passes the requested method in a parameter called '_method'.
Or, to quote directly from the docs you linked: "As a Ruby On Rails special, Prototype also reacts to other verbs (such as 'put' and 'delete' by actually using 'post' and putting an extra '_method' parameter with the originally requested method in there." TAG On Apr 9, 2007, at 2:55 PM, David Dashifen Kees wrote: > > I was under the impression that you could use DELETE and PUT with > prototype. In fact, the API indicates you can here: > http://prototypejs.org/api/ajax/options (just look for the method > option). That being said, I personally haven't found the need for > them > but if you need them they are there. > > -- Dash -- > > [EMAIL PROTECTED] wrote: >> I started toying with Prototype today. It's been sort of a kid in the >> candy store, "can I really do that? Woah!" fun afternoon. The $() >> operator, the sublime syntax for Ajax.Request, and the promise of so >> much more I haven't tried yet. >> >> I guess that's what frustrates me so much about intentionally sending >> the wrong type of HTTP request instead of a DELETE or a PUT. A >> POST is >> a POST, and not a DELETE, and not a PUT. Hiding the intended message >> type violates the REST principle of being a self-descriptive message >> at the protocol level. It also blocks the consumption of web services >> using POST/GET/PUT/DELETE to implement CRUD methods. >> >> Has anyone forked Prototype to fix this? >> >> >>> >> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
