<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.
I prefer .wos (since it's easiest/lightest in development), and I can always
fall back on an Objective-C implementation if performance is really an
issue...
- Matt
-----Original Message-----
From: Mark F. Murphy <[EMAIL PROTECTED]>
To: Multiple recipients of list <[EMAIL PROTECTED]>
Date: mercoled�, 17. marzo 1999 17:04
Subject: Performance Price Of Components
>
>Anyone have any experience with the performance price of reusable
components?
>
>I'd love to use components in my project where it makes sense. The docs
>seem to support taking this approach.
>
>Then when you read the tuning and deployment section, it talks about
>reducing your components.
>
>Any comments?
>
>Components seems the way to make the project development time go very
>quick.... I'm just worried about deployment.
>
>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
>
