There's been a bit of a discussion about it, if you care to check the archives.
You're right, but Safari doesn't recognize non GET/POST methods. It's been fixed in WebKit, but hasn't been distributed by Apple as an update to Safari. Rails (which I don't use--yet) does the translation automatically, so no harm done there. There is a ticket/patch in Trac to allow to programmer the option of forcing a particular method. I don't know what the plans are for it, but I know the devs are aware of it. http://dev.rubyonrails.org/ticket/6595 TAG On Apr 9, 2007, at 2:50 PM, [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 -~----------~----~----~----~------~----~------~--~---
