Hi Lorna,

I am wrestling with how to deal with nested resources. I understand your simple example above and from what I gather, the resource structure would look something like this to get the user's friends:
/user/123/friends/

So what happens if you want to even dig deeper?

/user/123/friend/1231/cats/

Do you just have to build for this? I can't think of an intuitive way to address this unless the cats becomes a filter inside a query string? I was reading somewhere else that it's also unnecessary to have many nested levels because you can just get these nested resources with an id but it's also my understanding with rest that it's meant to handle nested resources no matter how deep?

What do you think?