arborint wrote:The Model definitely does not "send any response back". But sending a response is not really role of the controller and should be done by the View or a Response object that post-processes the View in some way.
I think in general you can think of the Controller dealing with the request and the View dealing with the response.

Well then that actually seems a LOT more workable. Okay, okay. ^_^
arborint wrote:One of the great design questions in MVC is whether the Controller is a go-between for the Model and View, or whether the View can get the Model itself. I think we may want to delve into the issue a little deeper because there is not hard-and-fast rule.
I was playing around with that myself and so far, it feels as though the controller does it, but the data is actually being sent straight to the view. The controller is just the one that actually does the sending, so the model and view don't have direct access to one another and couldn't communicate without the controller.
arborint wrote:Techincally any application that generates a response and implements MVC has a View. An XML response to an Ajax call or outputting a PDF would both be done by "The View." In fact, that is the whole point. An application can have multiple "views" of the same domain information (Model) so that the same Model/Controller can respond with HTML, XML for Ajax, PDF, etc.
Whew, okay then. Everything I had read said that it was possible to 'skip' the model, but not the view or controller. Like, a form, in it's simplest form, is just VC, where it takes user input and does nothing to it other than displaying it. It isn't until form processing comes into the picture that the 'M' slips it's way in there.
I've already got my requests and such working very well, responses were the only thing I was having trouble with. So the response *is* the 'final result' of each MVC set, right? So I'd start at my front controller, send a request to my action controllers that all send their requests (if any), and then return their responses in the order that there requests were sent.
Ooh, but then, would the response object technically become a part of the model at that point (not the actual module, but like.. the 'M'

)?