> No. It has *nothing* to do with appearance. PUT is for updating an > existing resource (generally through a form).
and i am updating a resource... i'm not using #update_attributes, but in my controller I am saving. > I think that the need for a PUT link does not exist, period. If your > app is telling you that it wants a link, then it's telling you that it > wants a GET, perhaps with a custom verb or extra parameter. Destroy links are still the default in rails - destroy and put are similar in that they both change data. > Just never do PUT links (if you even *can* -- I'm not sure :method works > on links; I hope it does not). It does -- and from what I've read - the implementation is sound. I have a confirmation dialog on the link further narrowing the scope of things that could go wrong. > It's pretty clear if you read the class doc. That's a matter of opinion. Thanks for your help. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
