Hey Patrick, I understand the index action to list the resources and the show action to display a specific resource. This way I normally use both actions...
Cheers, Sazima On Dec 18, 1:22 am, "Patrick Doyle" <[email protected]> wrote: > I am curious what folks do with the #show action (and its associated view) > in a RESTful application. > > How often is it used? > > It seems to me that, for the sorts of applications I can envision, it > probably wouldn't be used much at all. Everything I might want to show can > be displayed by the #index action. Is that true more or less often than > not? > > If there isn't anything to be gained by a #show action, what do folks do (if > anything) to disable it? > > I have seen a use for #show in the classic case of a blog, where the index > page shows the titles of each of the entries in the blog, but the user must > click on one of those titles to "show" the actual blog post, but that brings > up a related (and nearly identical) question... > > I can see the same issue with the #new action for a nested route. Again in > the classic blog application, the #show action for the post would probably > include a form for adding a comment, thus eliminating the need for a #new > action (and its view) . > > What do you folks with vastly more RoR experience than I do in these > situations? Is there a best practice? Is there a common practice? > > --wpd --~--~---------~--~----~------------~-------~--~----~ 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 [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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
