Hmmm, good point there Erol On Oct 12, 12:14 pm, Erol Fornoles <[email protected]> wrote: > Hi Christian, > > On Oct 12, 3:47 am, Christian Fazzini <[email protected]> > wrote: > > > Bill has also indicated a very interesting fact. Being that index > > should display ALL records, while list can be used for more specific > > requests (i.e. to filter out results). I'll definitely give this a > > shot. Which I believe is also a RESTful approach > > The index should display ALL records, but then again it depends on the > context; if it is being accessed in a context of a parent-child > relationship (artist-painting), it certainly can be used to display > ALL records based on the parent (artist). > > It is a common "best-practice" in REST to define parent-child > relationships in the URI by slashes ("/"), rather than using a > querystring filter. This: > > /artists/DaVinci/paintings > > Is more RESTful than this: > > /paintings/list?artist=DaVinci > > Cheers,
-- 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.
