On Aug 10, 2009, at 3:17 PM, Jason King wrote:
> > On Aug 10, 2009, at 11:58 AM, Ryan Bates wrote: > >> GET /items/1/delete # => maps to delete action with confirmation >> screen >> DELETE /items/1/delete # => maps to destroy action >> >> If javascript is disabled it will fall back to a GET request and >> therefore display a confirmation screen. > > That's very tidy, +1 on that specific permutation. > > I presume the idea would be to have DELETE /items/1 still mapping to > destroy as well, for backwards compat (with a deprecation notice). If > not - then -1 :) I'd certainly hope there's not a deprecation notice - the 'DELETE / items/1/delete' is distinctly un-RESTful. The HTTP verb is sufficient - do we really want to be POSTing to /items/create and PUTting to / items/1/update (again)? --Matt Jones --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
