Let's say my API has the following routes:GET /theatersGET /theaters/:idGET /theaters/:id/moviesGET /moviesGET /movies/:idGET /movies/:id/theatersAnd then I have the following controllers with the listed methods:TheaterController    list    showMovieController    list    showI'm trying to decide in which controllers the remaining requests would best be handled from a strict RESTful perspective. Would thisTheaterController    listMoviesByTheater (handles GET /theaters/:id/movies)MovieController    showTheatersByMovie (handles GET /movies/:id/theaters)or thisTheaterController    listByMovie (handles GET /movies/:id/theaters)MovieController    listByTheater (handles GET /theaters/:id/movies)be more RESTful? If neither is more RESTful, which is a more common approach?Basically, the question boils down to whether TheaterController should only provide access to Theater resources and MovieController should only provide access to Movie resources.
Do RESTful API controllers typically only provide resources related to their own type?
rest;api design