I'd like to ask a simple controller design question regarding the MVC
pattern. It seems that most of the tutorials follow the
one-controller-per-table pattern. Books like AWDWR however use more
advanced approach. Unfortunalty AWDWR doesn't provide an answer how to
choose how many controllers to have and what methods to be included.
My question is how do you choose how to break the logic into controllers
and how you solve cases when the process is not oblivious (for example
if you have
two controllers using the same model).