[email protected] wrote in post #976295: > It seems from the rest of the etiquette on this forum I'm supposed to > tell you here to top-quote when replying ;p > > On Jan 19, 7:05pm, Mike C <[email protected]> wrote: >> Thanks for the link to the nested resource thing, it was an >> interesting read. So I take it that it's a good idea to define both a >> nested resource and an independent one for any resource that needs to >> be nested? > > It depends on the resource and how you want to access it, but I > generally do.
...whereas I generally use shallow nested resources: as/1/bs/new => creates B #10 bs/10/cs/new => creates C #25 cs/25 The ID is already sufficient to identify the resource; there's no reason to extend the URL unnecessarily. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [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.
