Is it appropriate in the MVC pattern for a controller to save state in any way.
Note, I realize that controllers do not save state on ASP.Net. I'm not using ASP.Net. I'm wanting to know if that pattern restricts this or not.
The pattern would have you save the state to the Model/models, not the Controller. The controller could modify the state, or the model could contain internals to modify it's own state.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With