title: RESTful API design with associations
body: <p>I'm attempting to build an API for two resources, one with Users, and the other with Movies. Both resources have associations -- a User will have multiple Movies, and a Movie will have multiple Users. Presumably, I'd design my API something like this: </p>
  
  <pre><code>/api/users/
  /api/users/:id
  /api/users/:id/movies
  
  /api/movies/
  /api/movies/:id
  /api/movies/:id/users
  </code></pre>
  
  <p>But here's the issue: I'm also using Backbone.js on the client side to fetch the API data. If If I create a Collection at</p>
  
  <pre><code>/api/users/:id/movies
  </code></pre>
  
  <p>then this will work well for GET requests, but POST and PUT requests would seemingly then be directed at:</p>
  
  <pre><code>/api/users/:id/movies/:id
  </code></pre>
  
  <p>But, seemingly, it would be better if it was posted to </p>
  
  <pre><code>/api/movies/:id
  </code></pre>
  
  <p>instead. Is that correct? How do people generally deal with RestFul associations? </p>