I have a quick Alloy framework question for everyone. I saw in a few of the examples on GIT (in particular the login example within the Models), that there are references to placing functionality such as login/logout/authentication, etc within the model itself, rather than within the controller, and simply calling the model's functionality from the controller. I am curious if this is simply an Alloy best practice? I have come from the WPF (MVVM), and ExtJS (MVC) world, where the model literally only was a POJO like model, which contained the column definitions, but no functionality (other than basic converters and the like), and the controllers or View Models handled tying the Views to the Models, or issuing network calls. I noticed in the examples, the author mentions making network calls directly from the models, which is counter intuitive to my thinking on MVVM/MVC.
Is this an Alloy best practice? Just curious. Also, is there any performance implication here with this approach? Curious for everyone's thoughts/experience.
Hope all are welll Chris