I'm no expert on this but, I would say memory/design principles.
A module extends LayoutContainer, where as Application is the whole shabang.
Loading multiple Application instances into another Application using
SWFLoader is bound to take a lot more memory.
I think compilation of modules directly relates to how you 'design' your
main application's architecture.
Think about this, if you can design modules in a way that encapsulates what
changes into 'modules' and keep logic out of them that doesn't, compilation
will speed up.
I'm really talking about class architecture, using factories, getting 2 or 3
levels of abstraction. This is what I do and it works well.
Mike
On Wed, Oct 1, 2008 at 5:41 AM, Manu Dhanda <[EMAIL PROTECTED]>wrote:
>
> Hii Guyz,
>
> My question is regarding the modular applications.
>
> What will be the performance or logical effect on the application if we
> will
> use small applications as modules under a big wrapper application?
>
> The benefits I see here is maintenance is easier. While you are making any
> changes to any (modular) application, your other applications will be
> un-affected and to me, it reduces compilation time to a major extent.
>
> I would like to get the other expert opinions.
>
> Thanks,
> Manu.
> --
> View this message in context:
> http://www.nabble.com/Module-vs-Application-tp19757230p19757230.html
> Sent from the FlexCoders mailing list archive at Nabble.com.
>
>
>
--
Teoti Graphix, LLC
http://www.teotigraphix.com
Teoti Graphix Blog
http://www.blog.teotigraphix.com
You can find more by solving the problem then by 'asking the question'.
