I'm curious, what is NOT MVC?
or more precisely - In a MVC-using app, what is everything else apart form MVC?
I see the tendency to start explaining MVC in a form of
Separate the application into three parts[...]
Which seems to suggest that you should try to fit in as much as you can (or all) of your design under either Model, View or Controller.
Yet, it's easy to see that in most explenations MVC is primarily described as a user interface design. How in this situation do I treat non-UI elements?
- Do I bend definitions of non-UI elements and try to figure out whether they could fit to either Model or Controller?
- Is there a separete description in MVC design that deals with non-UI elements?
- Is there a description of how MVC interacts with such elements? Is it all through Model? All through Controller?
I'm wondering how do I treat the part of my application which is used only for monitoring my local network and storing the information in a database. It has no UI related functionality and its sole puprose is to fill in the database with file related information, which then in turn is presented to the user through the web interface.