Controller Partitioning

Topics: Web Guidance v-Next (not WCSF)
Dec 18, 2009 at 4:14 PM

One question that came up in the teamroom is how to partition our controllers. We put a TON of functionality for our Music Store web app in a SongsController. Sounds reasonable but it had search, rating, reviewing functionality. Should each of these separate pieces get their own controller? One school of thought is that each main entity should get it's own controller that would encapsulate all related CRUD operations. Another school of thought is that the controller is more aligned with the UI. Each screen ultimately would get its own controller.

What do you think?