Hi,

Actually my biggest concern, which I have voiced previously, is that 
this idea of mapping each request to a single method inside a single 
module is not very good. Most pages obviously require the output of 
several logical units of code (main page, navigation, user information, 
teasers, banners etc.). It only really works well for AJAX requests.

Using multiple modules is too costly in symfony, due to re-execution of 
too many steps in the filter chain. Pushing this into components does 
not make sense, since these do not allow direct user interaction, 
requiring the need for "dummy modules" that only serve the purpose of 
calling components. The entire component slot idea also pushes way too 
much power into templates, as suddenly the template decides when and 
where components/modules are getting loaded.

As a result Matthias (and to a lesser extend I) have been pondering up a 
PageController [1], where one would optionally have the ability to map a 
request onto a virtual page. This page would know what modules to call 
(optionally with preset parameters), it would by pass reexecuting 
redundant steps in the filter chain. The output if the modules could be 
placed into arbitrary locations inside the layout template. This way you 
also have a central place to look at, to find out where what modules are 
getting called, instead of having to dig through your templates when it 
comes time to refactor things.

However Matthias just told me that he has given up on hacking this 
PageController into symfony as a plugin, because its simply too hard to 
work around this one module/method per request assumption. Of course the 
goal must be to allow most the classic mode (perfect for AJAX requests 
and simple prototypes) and this expanded mode.

regards,
Lukas

[1] http://trac.symfony-project.com/trac/wiki/sfPageControllerPlugin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to