In WO3.5.1 there as a significant price for nesting components
especailly if they were in long repetitions. Forget about that it WO4.
The price for nesting is near zero. Now don't go nesting stuff within
stuff with no good reason. I suppose nesting 10 levels deep will start
to soak a few cycles. But also don't be afraid to factor and
componentize as much of your system as you feel is reasonable.
d
"Mark F. Murphy" wrote:
>
> At 5:34 PM +0100 3/17/99, Matt Kerr wrote:
> ><random thoughts - no empirical data...>
> >
> >I would say long response times correlate more closely with large
> >repetitions than with deep component nesting. (eg. 100 reps vs. 1 pass at
> >~half dozen components...)
> >
> >If you have a lot of repetitions, or large repetitions, you may want to
> >flatten out your component hierarchy.
>
> Well, I'm not going deep at all on the components.
>
> Just a Parent Component for the entire site... which will be comprised of
> the branding component, user component, and advertising component.
>
> Each page in the app will use the parent componet and the "content" will be
> based on the page.
>
> So I'm not talking a lot of components. Just enough to maek the site very
> flexible in design and allow for site wide mods.
>
> I just didn't want any of my development strategy to get in the way of a
> deployment/performance strategy.
>
> Thanks.
>
> mark
> ---------------------------------------------------------------------------
> Mark F. Murphy, Director Software Development <mailto:[EMAIL PROTECTED]>
> Tyrell Software Corp <http://www.tyrell.com>
> PowerPerl(tm), Add Power To Your Webpage! <http://www.powerperl.com>
> ---------------------------------------------------------------------------
> Member of Families Against Internet Censorship: rainbow.rmi.net/~fagin/faic
