2008/6/20 Sean Davis <[EMAIL PROTECTED]>: > Therefore, I was planning on a web/web- > services approach using REST approaches. It seems that dealing with > single collections is pretty straightforward, but I have a couple of > questions: > > 1) What is the "standard" for filtering a single collection > (specifying some fields and some match criteria like "begins_with", > etc.)?
I guess appending a query string to your resource collection path would be OK, wouldn't it? (ie: /authors/12/books?begin_with=foo) > 2) How does one deal with relationships between collections? It > looks like nested urls like: > > http://example.com/author/12/books > > are the correct way to handle this, but could someone enlighten me on > whether or not there is a standard? Routes has support for nested collections: http://routes.groovie.org/class-routes.base.Mapper.html#resource Look at the parent_resource argument. It seems to suggest that the standard would then be /authors/12/books. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
