Hi All
Lately I've been doing some restructuring on a site to improve
performance and was wondering if there is any overhead involved when
dynamically constructing a page from many smaller dynamic components
using 'includes' as opposed to having all the code in the same page.
(For example, a product list page has the product summary component
as an 'include' inside a loop).
In the background I've been busy learning fusebox as I plan to
ultimately convert the site in the future so I've been using the
fusebox naming conventions and structuring the site as much as
possible into fuseactions, circuits, fuses, display code and layout
code (by the way, I've found this process unexpectedly smooth)
without actually deploying the fusebox infrastructure in Active 4D
(who's huge added value I'm now starting to appreciate).
I thought that maybe Active 4D doesn't cache the included modules
(say, the way it does libraries) and so it might be slower for the
moment than a monolithic page where there are many iterations.
Also, what is the recommended way to pass properties set by a
fuseaction to a display component ? (for example, the
fuseaction . . . 'act_DoaQuery.a4d' . . . sets some properties and
the display component 'dsp_showCatalog' wants to read these
properties and modify it's own logic based on them. Is a collection
the way to do this ? Where is best to initialise it ?
Sorry if I've mis-used the terminology, I'm learning it on the train
at the moment and still have huge gaps in my knowledge :)
Can someone put my mind at rest enough for me to let rip with this
approach, particularly regarding the performance aspect ?
Thanks.
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
