Michael Pavling wrote: > On 14 April 2010 23:23, David Zhu <dzwestwindso...@gmail.com> wrote: >> But i was just wondering, by adding that confirm action in that >> controller, does it violate the Restful Resources rules? > > It does break the principles of REST, but if you're not that worried > about being RESTful, there's no problem. > > If you do want to follow rest, instead of putting the confirm action > in the ProductController, create a new controller > (ProductConfirmController, maybe) that does the functions of the > confirm in it's create method.
Or add a virtual attribute to the object that indicates whether confirmation is required. A second controller is unnecessary and IMHO not particularly RESTful. OTOH, there is nothing unRESTful about having extra controller actions if your application needs them. The big 7 actions are not magical. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. -- 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.
