It depends on your project's design to some extent.
It has all the preformance downsides of using requestAction but this
can be helped by caching the views in some cases.
On the up-side you can have a setup where the home-page does not need
to be altered whenever a module is added, removed or
Thanks
RequestAction is good instead of $uses = array('module1', 'module2',
'module3', 'module4',
'module5');, is it your mean?
On Sep 23, 11:59 am, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
This kind of portal-page is one place where I have put requestAction
to good use. In combination with
This kind of portal-page is one place where I have put requestAction
to good use. In combination with caching, it works pretty well.
The main benefit is that each independent module (mine are plugins)
can internally decide what to render and show on the front-page. The
front-page does not need to
Hi,
I am working on a dynamic content website. I want to implement home
page. This home page
of my site needs to have a lot of dynamic content generated on it.
Dynamic contents are coming from different module.
I have implemented it like this.
1 Make HomesController
2 Use of $uses =
there are other, more robust ways to accomplish this, for example by
using cached data.
but really, make it work, then make it work better. keep in mind that
this might be something you'll revisit later, i wouldn't get too hung
up on the performance, because it sounds like you are pretty early
