Quoting Colin Law <[email protected]>: > > 2009/7/10 Jeffrey L. Taylor <[email protected]>: > > > > My Web application has several contexts where a collection of ActiveRecords > > is > > rendered. If the URL contained the partial and/or layout, the several > > controller methods could be collapsed into one. What hazards, etc. lie that > > way? > > I, for one, do not understand what you mean. Could you give a more > detailed description, with example? > It's an RSS readers. Users have feeds that have articles. A list of articles can appear in about four contexts: a paginated flat list of all unread articles, a flat list of articles found by a search. list of all unread articles indented under a feed (with collapse/expand icons), a list of all read articles under another type of header. Currently all of these have their own action method under two different controllers.
I think it is feasible to have one action method that is passed the selection criteria (unread, read, etc. articles) and a layout or partial template to render thru the URL. Beyond the obvious SQL injection protection and restricting the template/layout to a known set of reasonable values, what hazards (security, maintenance, etc.) lie this way? I think I can move towards and possibly achieve a RESTful API with a bit of squeezing state and context into the URL. Does this way lie madness/dragons? TIA, Jeffrey --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
