Should you have multiple controllers in an AS3 MVC implementation?
I am creating a very simple game in AS3 as an exercise in pure MVC.  The application will have 3 views: a start/replay screen, a score/time display and the actual game area.  

There is an obvious separation between the start screen and the other two elements that are active during game time, so should there be two controllers, one to handle game events and one for out-of-game events?  Or is it bad practise to have multiple controllers in a very small application?

Should you have multiple controllers in an AS3 MVC implementation?
===

I am creating a very simple game in AS3 as an exercise in pure MVC.  The application will have 3 views: a start/replay screen, a score/time display and the actual game area.  

There is an obvious separation between the start screen and the other two elements that are active during game time, so should there be two controllers, one to handle game events and one for out-of-game events?  Or is it bad practise to have multiple controllers in a very small application?
