Modules are a grouping mechanism for actions (controller) and their associated templates (views). Actions can access the model classes (model) to get the data needed by the templates (view), which is why the action is the controller; it controls recieving an incoming request (link clicked, form submitted, etc), extracting data from models based on what was sent with the request, formatting data for the templates and then passing that data to the templates to render the response.
On Tuesday 18 May 2010 01:50:49 Dennis wrote: > So anyone seen a definitive pictogram that shows all the elements of > Symfony in relation to an MVC implementation? Something like a Venn > diagram showing which element of symfony belongs in which part of pure > MVC? > > I'm kind of wondering most of all: > What role in MVC does a module perform? > Is is possible to disable/enable/add filters per module? > > TIA, Dennis -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
