>
>
> However, suppose the content editors want to write an article about
> farmers markets and they want to display a list of farmers markets in the
> local area, we can tell them to embed something like
> {/organizations/list/tag:farmers-markets/radius:10/count:5} in the content.
> Or somewhere else they want a list of music events, then we would tell them
> to embed {/events/list/tag:music/radius:75/count:10}. So by passing that
> URL to requestAction, it will call the appropriate controller and action
> and return the rendered content. It keeps the code simple and modular, in
> the spirit of MVC.
>
What I am suggesting is slightly different... instead of having *one*
requestAction *for each* of the modules you need included, I suggest to
have only *one* requestAction *for all the modules on the page.* This would
cut the overhead of rebuilding the Cake API for every module on the page.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/cake-php
