I would like to know the following in Android development using MVC, for each Activity I have to have a Controller and maybe a DAO? Or can I use the same Controller class that controls two Activity? And does it lose a lot of performance or do it weigh heavily create so many classes? The model I know I can use in other controller and Activity.
I'm also having to always pass my controller to DAO, since I need to wait for a callback in a thread and then after the end I ask DAO to call a method of this controll that was passed by parameter. For example,% with% where in this method it would check the exception and possibly ask to display something using some method of the view (which was also passed as parameter in the controller). Is this right? I've been reading quite a bit about MVC - MVP on Android but I get confused when I'm using a Database.