Where does form processing logic belong in a MVC web application?

Question

In a web-based application that uses the Model-View-Controller design pattern, the logic relating to processing form submissions seems to belong somewhere in between the Model layer and the Controller layer. This is especially true in the case of a complex form (i.e. where form processing goes well beyond simple CRUD operations).

What's the best way to conceptualize this? Are forms simply a kind of glue between models and controllers? Or does form logic belong squarely in the M or C camp?

EDIT: I understand the basic flow of information in an MVC application (see chills42's answer for a summary). My question is where the form processing logic belongs - in the controller, in the model, or somewhere else?

Answer 1

I'd say this should probably be seen as 2 separate actions...

1. submitting the form (V -> C)
2. processing the submission (C -> M)

Speaking in generics, I tend to think as each action as a message between the sections. The full series of messages would be something like this...

• Display Form (C -> V)
• Submitted by the user (V -> C)
• Process contents (C -> M)
• Processing finished (M -> C)
• Display Results (C -> V)